Page 3 of 3
Re: MailScanner Unable to Call SpamAssassin
Posted: 23 Oct 2011, 22:00
by Sarah
According to the output, sa-learn is still working: "Learned tokens from 1 message(s) (1 message(s) examined)" - that indicates success.
Re: MailScanner Unable to Call SpamAssassin
Posted: 24 Oct 2011, 20:10
by Serra
One thing I did notice is that the ALL_TRUSTED flag has changed from 0 to -1. I was using ALL_TRUSTED to identify local mail, but now all mail from SMTP shows up under ALL_TRUSTED. This seems to make more spam go through since it is hitting most spam with a -1.
Re: MailScanner Unable to Call SpamAssassin
Posted: 24 Oct 2011, 22:10
by duncang
You will need to roll back NetAddr::IP by one version as there seems to be some sort of incompatibility with SA, a similar issue was noted this time last year. From what I've seen SA does not function correctly and it will let very high levels of spam through incorrect marking.