Inconsistent SpamAssassin report
Diederik van den Burger
diederik at webrelated.nl
Mon Feb 6 15:04:33 UTC 2017
Recently I have installed MailScanner on our email server. All seems to be working fine except the integration with SpamAssassin. Several emails are not marked as spam which definitely are spam. At first I thought the problem could be solved by adding extra rules to my SpamAssassin config, but this is apparently not working. When I check the spam emails through MailWatch, I see the following tests were ran:
BAYES_00, DCC_CHECK, FREEMAIL_FROM, RCVD_IN_DNSWL_BLOCKED, RDNS_NONE, SPF_SOFTFAIL, URIBL_BLOCKED, URIBL,RHS_DOB with a total score of 5.08.
However, when I run:
spamassassin -t -d < spamemail
I get a report saying the following tests were ran:
URIBL_RHS_DOB, URIBL_BLOCKED, RCVD_IN_RP_RNBL, FREEMAIL_FROM, SPF_SOFTFAIL, BAYES_50, PYZOR_CHECK, DCC_CHECK, RDNS_NONE, DIGEST_MULTIPLE with a total score of 11.9.
So it seems like MailScanner runs a whole different version/instance of SpamAssassin. How do I go about solving this?
More information about the MailScanner