Spamassassin time outs

[Matt Kettler]

At 12:04 PM 1/21/2005, Philip Parsons wrote:
>Ever since we upgraded to spamassassin 3.02 in the maillog we are getting
>a lot of
>
>"Spamassassin timed out and was killed, failure "
>
>There does not seem to be any reason for this that I can find anyone got
>any idea's ???

1) make sure the AWL is off.. you need to do this at the spamassassin
level, as SA 3.0's API does not respond to MailScanner's attempts to
disable it. The extra DB overhead here can be substantial.

2) Are you using bayes? Check for "expire" files next to your bayes
database files.. If you have those piling up, MS is timing out SA while
it's doing bayes database expiry. Either disable bayes_auto_expire and run
sa-learn --force-expire from a cronjob, or extend your spamassassin timeout
to a really large value.

3) SA 3.0 queries a lot more RBLs.. run spamassassin --lint -D and see if
it's getting hung up there.

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ (http://www.mailscanner.biz/maq/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!