> It is not clear from your description if spam checking is enabled at all.
Surely messages such as this in my logs provide evidence amavis is running ?
'Nov 20 07:52:50 foobar amavis[24956]: (24956-15) Passed CLEAN
{RelayedInbound}, [X]:15896 [X] <X> -> <X>, Queue-ID: X, Message-ID: <X>,
mail_id: X, Hits: -, size: 631762, queued_as: X, 197 ms'
> Did you modify 15-content_filter_mode?
No. I follow best practice and put all my edits in '50-user', I do not touch
other config files.
>
> Am 20.11.19 um 08:28 schrieb Laura Smith:
>
> > I am aware the usual answer to this question resolves around setting
> > $sa_tag_level_deflt = -9999; which is not the case for me (i.e I know how
> > it works, and I'm migrating a known-good config).
> > I am migrating a mail instance from Alpine Linux to Debian 10.2. Debian
> > 10.2 packages amavis 2.11.0.
> > My config on Apline works perfectly and the spam score headers get added as
> > expected, however moving the config accross to Debian, the headers cease to
> > be added.
> > amavisd is otherwise working perfectly on Debian (i.e. mails are flowing
> > correctly and I can see amavisd doing its work in /var/log/mail.log)
> > The contents of my /etc/amavis/conf.d/50-user file is as follows:
> > use strict;
> > $myhostname = '//REMOVED FOR SECURITY//';
> > @inet_acl = qw( 127.0.0.1 [::1] //REMOVED FOR SECURITY//);
> > @mynetworks = qw( 127.0.0.1 [::1] //REMOVED FOR SECURITY//);
> > $allowed_added_header_fields{lc('X-Spam-Report')} = 1;
> > $warnvirusrecip = 1;
> >
> > Spam Actions
> >
> > =============
> >
> > $sa_tag_level_deflt = -9999; # insert spam headers
> > $sa_tag2_level_deflt = 5; # when to tag email
> > $sa_spam_subject_tag = 'MAYBE SPAM';
> > $sa_kill_level_deflt = 11.5; # Triggers ultimate Actions
> > $final_bad_header_destiny = D_PASS;
> > $final_spam_destiny = D_DISCARD;
> > @local_domains_maps = ([//REMOVED FOR SECURITY//]);
