mc-exim and mc-mailscanner failed to install

[mdio33]

Hello all.

I'm trying to test MailCleaner on Debian 12, but after runing "debian-bootstrap/install.sh" i've got this error and apt-get install -f does not solve.

Finished with errors:
x These packages failed to install: mc-exim mc-mailscanner You can try to fix by running apt-get install -f then running this script again
Please try to remedy these errors, report them as needed, then run this script again to verify that there are no remaining errors with the installation.
Creating bare mailcleaner configuration file...
Bootstrapping complete. Please run the following command for the MailCleaner Installation Wizard:
/usr/mailcleaner/scripts/installer/installer.pl

Also, when I try do run "apt-get update" got this errors and I not abble to continue...

Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 https://download.docker.com/linux/debian bookworm InRelease
Get:5 http://cdnmcpool.mailcleaner.net bookworm InRelease [4,317 B]
Err:5 http://cdnmcpool.mailcleaner.net bookworm InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 14BDC38F38BE9807
Hit:6 https://download.opensuse.org/repositories/home:/voegelas/Debian_12 ./ InRelease
Reading package lists... Done
W: GPG error: http://cdnmcpool.mailcleaner.net bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 14BDC38F38BE9807
E: The repository 'http://cdnmcpool.mailcleaner.net bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Some help is appreciated.
thanks

[JohnMertz]

Hi!

Installing our packages requires that the GPG key is first installed. This should be done earlier in the bootstrap script, but this is likely failing because we recently changed the CDN where this key is hosted and I have not updated the relevant paths in this repo. I'll do that today.

Note that the installation of MailCleaner Next should get significantly easier in a couple of weeks, including potentially just having VM images available. So while I'm thrilled that you want to help test, you may want to wait a little bit longer.

[mdio33]

Hello John,
Thank you for your answer and if is it so, I will happly wait. :)

[mdio33]

Hello John,

Any news about the new instalation of MailCleaner Next?
TY.

[JohnMertz]

Hello,

Sorry. The news is fairly limited right now. We hit a bit of a labour crunch and I've been spending 80% or more of my time on support and other internal efforts. The remainder of my time has been spent working on tools to improve our Bayes results since we're receiving a lot of negative feedback on that right now.

I'll certainly be back to Next but I can't give any timelines. Note however, that I'm putting some consideration into re-basing Next on Debian 13 since the freeze dates for it have been announced and we realistically will not have a Stable release on 12 ready too long before Debian 13 goes stable. From a glace, it seems that nothing in the upgrade to 13 should require any extra fixing that isn't already needing to be fixed in 12. We should still have our Beta images available while Debian 13 is still in testing, but it may change how long we hold back the Stable release.

I'll try to provide an update here when I'm back to putting significant time into Next, but that will probably be another couple of weeks at this point.

[mdio33]

Hello and thank you for the feedback.