Ole Nomann Thomsen wrote:
> Hi, can I ask a small favor from some of you running SA with Bayes enabled:
> Please run the following perl-oneliner on your SA-log (mine is "current"):
>
> perl -ne 'if (/result:/) {$n++; $b++ if (/BAYES/);} } print $b/$n,"\n"; {' <
> current
>
> (I promise it's not a rootkit :-)
Modified to support mailscanner:
perl -ne 'if (/spam, SpamAssassin/) {$n++; $b++ if (/BAYES/);} }
print $b/$n,"\n"; {' < /var/log/maillog
Note: this will match both spam and nonspam log lines for MailScanner, and I do
have logging of non-spam turned on in my MailScanner setup.
I get:
0.965083118870418
As others have pointed out, I too use bayes_ignore_to/from on this list, as well
as the MailScanner list.
I have 503 non-bayes matching emails in my logs. Of those 503, all but 14 can be
attributed to my bayes_ignores.. The remaining 14 are SpamAssassin timeouts.
Such as this:
Feb 1 22:40:08 xanadu MailScanner[14477]: Message k123U5En007816 from *MUNGED*
(*MUNGED*) to evitechnology.com is not spam, SpamAssassin (timed out)
(FWIW: I have a 10 minute SA timeout, and I have bayes_auto_expire disabled in
local.cf. However, timeouts usually appear to be that SA did an auto-expire
anyway.. *grumble*)
