> That seems odd.� Are you running BigEvil? � Yes, I was.
That's probably the problem
When procmail is calling SpamAssassin and a large number of messages come in, SpamAssassin may occasionally fail to run, perhaps because the load exceeds the allowable quota. Procmail then recovers the mail and continues with the procmail script, but with the message having gotten no SpamAssassin markup whatsoever. The solution is to add a second SpamAssassin invocation to procmail in case the first one didn't work.
Well, this is bullcrap, if your system is so low on resources that spamassassin times out, running it AGAIN is not helping anything. The solution is to use spamc/spamd instead.
:0fw: spamassassin.lock * < 256000 | spamassassin
# Try a second time if SpamAssassin failed
:0
! ^X-spam-level:.*
* < 256000
{
LOG="RUNNING SPAMASSASSIN AGAIN
"
:0fw: spamassassin.lock2 | spamassassin
}
And then see how often that fires.
But you should be using spamc with spamd as it is much faster and more efficient.
-- May you live in interesting times
smime.p7s
Description: S/MIME cryptographic signature
