Inconsistent SpamAssassin report
Diederik van den Burger
diederik at webrelated.nl
Tue Feb 21 13:14:07 UTC 2017
I just wanted to give an update on this. The problem actually was two-fold. For some reason, postfix did not have the correct permissions to run the Pyzor and Razor tests, hence the first difference. For future reference, I debugged this using the following command:
sudo su postfix -p -c 'spamassassin -D -t -d -p /etc/MailScanner/spamassassin.conf < /spam/file.txt'
-D is obviously debugging, -d removes any existing spam reports, -t enables test mode and I did not use -c but -p to pipe in the preferences.
Scrolling through the output it became evident that there was a permission error.
The second issue was completely my own fault and I almost feel stupid for admitting it. I sometimes saw differences in bayes scores. This was because I had a cronjob automatically learning files that were marked as spam. So when they first came in through MailWatch, they hadn't been learned yet but afterwards they had been, obviously raising the score.
I felt like it was necessary to post this update, specifically the first part, since this might help people in the future.
> On 7 Feb 2017, at 20:10, Mark Sapiro <mark at msapiro.net> wrote:
> On 02/07/2017 10:39 AM, Peter Lemieux wrote:
>> I can see running the incoming daemon as the postfix user, but I don't see
>> any reason to run MailScanner itself that way.
> MailScanner runs as the postfix user so it can dequeue messages from
> Postfix's hold queue and after scanning queue them in Postfix's incoming
> Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
More information about the MailScanner