|
> That seems odd. Are you running BigEvil?
Yes, I was.
> > *** The /etc/procmailrc file: > > > > DROPPRIVS=yes > > > > :0fw: > > * < 200000 > > | /usr/bin/spamassassin > > > > :0fw: > > * ! ^X-Spam-Level:.* > > * < 200000 > > | /usr/bin/spamassassin > > Why are you running every non-spam through SA twice? I created that setting from an FAQ on wiki.apache.org. Here is the
text from that page:
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.
: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 Is this not correct? |
- Re: General Comment - SA is ... Justin Mason
- Re: General Comment - SA... Jeff Chan
- Re: General Comment - SA... Simon Byrnand
- Re: General Comment - SA... Jason Haar
- Re: General Comment - SA... Daniel Quinlan
- Re: General Comment - SA... Bob Apthorpe
- Re: General Comment - SA is proce... Daniel Quinlan
- Re: General Comment - SA is ... Jeff Chan
- Re: SA is processing messages slowly Daniel Quinlan
- Re: SA is processing messages slowly LuKreme
- Re: SA is processing messages slowly ed
- Re: SA is processing messages slowly Marco van den Bovenkamp
- Re: SA is processing messages slowly LuKreme
- RE: SA is processing messages slowly Chris Santerre
