disabling RBL checks and SpamAssassin time out errors

Matt Kettler mkettler at EVI-INC.COM
Thu May 29 23:05:01 IST 2003

In your case, it sounds like the RBLs are not the cause of the problem..

I'd try running spamassassin on the command line with debug output turned
on and see where it "sticks".. RBLs are by far the most common sticking
point that causes SA to take too long, but razor, dcc, pyzor, certain
configfile typos, and other things can also wedge it up for a bit of time..

spamassassin -tD <sample-spam.txt

(sample-spam.txt comes in the SA tarball).

You'll probably have to copy the spam.assassin.prefs.conf from MailScanner
to ~/.spamassassin/user_prefs while running this test to have it act the
same as when MailScanner calls it...

It's also a good opportunity to lint your config files

spamassassin --lint

At 05:01 PM 5/29/2003 -0400, Vasantha Narayanan wrote:
>I'm running MailScanner-4.20-3 with SpamAssassin-2.50 on a Solaris 2.8
>I do not want SpamAssassin to do RBL checks.  I've set "skip_rbl_checks 1"
>in  spam.assassin.prefs.conf.  But yet, it seems as though RBL checks are
>indeed being done.  I get the following error -
>"MailScanner[3708]: SpamAssassin timed out and was killed, consecutive
>failure 1 of 20".
>I read in the archives that this error can be avoided if SpamAssassin
>Timeout is set to 40 and Scanner timeout is set to 10.  But this already
>seems to be the default.
>Any tips on what is causing this error and how to avoid it?  Is this caused
>by RBL checks?  If so, what more needs to be done to disable it?

More information about the MailScanner mailing list