In Debian, 15-content_filter_mode has the following comment :
# Default SPAM checking mode # Please note, that anti-spam checking is DISABLED by # default. # If You wish to enable it, please uncomment the following lines: @bypass_spam_checks_maps = ( \%bypass_spam_checks, \@bypass_spam_checks_acl, \$bypass_spam_checks_re); And this is how I enable spam checking with spamassassin.The default behavior is to start w/o antivirus or antispam control. Best, --Yassineviber : +213-779 06 06 23http://about.me/ychaoucheLooking for side-gigs. On Tuesday, December 16, 2025, 12:41:17 PM GMT+1, Damian <[email protected]> wrote: There is no mention that I can find in my amavisd configuration of spamassassin but my mail log is full of messages like: Dec 13 16:30:16 mustang amavis[178016]: initializing Mail::SpamAssassin (0) Dec 13 16:30:18 mustang amavis[178016]: SpamControl: init_pre_fork on SpamAssassin done Dec 13 16:30:18 mustang amavis[178016]: extra modules loaded after daemonizing/chrooting: Mail/DKIM/ARC/MessageSignature.pm, Mail/DKIM/ARC/Seal.pm, Mail/DKIM/ARC/Verifier.pm, Mail/SpamAssassin/Logger/Amavislog.pm, Mail/SpamAssassin/Plugin/DMARC.pm, Mail/SpamAssassin/Plugin/FreeMail.pm, Mail/SpamAssassin/Plugin/HashBL.pm, Mail/SpamAssassin/Plugin/SpamCop.pm, Mail/SpamAssassin/Plugin/WelcomeListSubject.pm, Net/Cmd.pm, Net/Config.pm, Net/SMTP.pm How can I stop this? You could try to override the default @spam_scanners setting, e.g. with @spam_scanners = ();
