On Sat, 17 Jul 2004 16:28:16 -0700 "Dan Kohn" <[EMAIL PROTECTED]> wrote:
> I've seen this behavior on overloaded servers. I created a wiki page to > describe the fix. Please let me know if it works. > http://wiki.apache.org/spamassassin/NoProcessOnOverload Unfortunately it was of no help. Two things could be happening: 1) Email starts getting scanned by SA but the server kills it due to excess cpu usage or memory. Then email is directly delivered to pop3 account without procmail running any other rules (thus skipping second SA check). 2) Email starts getting scanned by SA, but SA has a problem with this particular email (bad headers?), SA quits with some error code that procmail doesn't understand, thus it stops processing any other rules and just delivers the email directly to the pop3 account. Any ideas how to check the return code of SA?
