>> did you reload/restart amavis after installing new SA?
>> This header is added by amavis which uses SA libraries internally.

On 30.05.22 09:50, Alex wrote:
>Yes, thanks. This has been ongoing for weeks.

doesn't amavisd by any chance use old SA installation/libraries?

On 30.05.22 15:12, Alex wrote:
I don't think so - the current paths it uses are:

/usr/share/spamassassin
/var/lib/spamassassin/4.000000/updates_spamassassin_org
/var/lib/spamassassin/4.000000/kam_sa-channels_mcgrail_com
/etc/mail/spamassassin/

these are rules, not libraries.
there is a possibility that you have multiple versions of SA installed and amavis uses the old one.

try running:

% locate SpamAssassin.pm DMARC.pm

to see if there are some that shouldn't be...

If I understand Kevin's comments correctly, we know there are still DMARC
problems. I think maybe this is related?

$ spamassassin -t -D DMARC < dmarc-reject1 2>&1|grep -i dmarc
May 30 14:59:14.894 [1250699] dbg: DMARC: using Mail::DMARC::PurePerl for
DMARC checks
May 30 14:59:15.034 [1250699] dbg: DMARC: result: pass, disposition: none,
dkim: pass, spf: fail (spf: pass, spf_helo: fail)
       DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DMARC_PASS,

it hit DMARC_PASS, which is the opposite of DMARC_REJECT or KAM_DMARC_REJECT.

So it did hit __KAM_DMARC_POLICY_REJECT but just not whatever else was
necessary to fulfill the requirements for the KAM_DMARC_REJECT when run
with SA manually.

__KAM_DMARC_POLICY_REJECT only says that the sender domain has DMARC policy set to reject, it does not say that the mail is to be rejected

--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Linux is like a teepee: no Windows, no Gates and an apache inside...

Reply via email to