spamassassin-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From spamassassin-...@incubator.apache.org
Subject [SpamAssassin Wiki] New: NoProcessOnOverload
Date Sat, 17 Jul 2004 23:25:23 GMT
   Date: 2004-07-17T16:25:22
   Editor: DanKohn <dan@dankohn.com>
   Wiki: SpamAssassin Wiki
   Page: NoProcessOnOverload
   URL: http://wiki.apache.org/spamassassin/NoProcessOnOverload

   Created new page answering FAQ

New Page:

= Procmail and SpamAssassin seem not to process some of my messages when the load gets too
high =

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.  This results in a false negative if the mail is
spam.  The solution (other than moving to a more powerful server, which also works) is to
add a second SpamAssassin invocation to procmail in case the first one didn't work.  Compare
to the default script shown at UsedViaProcmail.

I has this problem on an overloaded machine (and so switched to a better hosting service),
and this solution completely solved the problem until I switched:

{{{
:0fw: spamassassin.lock
* < 256000
| spamassassin

# Try a second time if SpamAssassin failed

:0fw: spamassassin.lock2
* ! ^X-Spam-Level:.*
* < 256000
| spamassassin

:0:
* ^X-Spam-Status: Yes
probably-spam
}}}

== Contributors ==

 * DanKohn

Mime
View raw message