Debugging SA timeouts

[Rick Cooper]

> -----Original Message-----
> From: MailScanner mailing list
> [mailto:MAILSCANNER at JISCMAIL.AC.UK]On
> Behalf Of Martin Hepworth
> Sent: Wednesday, March 10, 2004 4:56 AM
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: Debugging SA timeouts
>
>
> Hi
> Anyone got any good ways of debugging SA timeouts and
> finding out whats
> going on..
>
> apart from the obvious of using MS and SA debug mode
> in MailScanner.conf!!!

Change to the home dir of the user that runs SA in your MS config
su to that user (you don't *have* to run as the normal SA user
but it will wack out your bayes tests if you don't)

spamassassin -D -p
/opt/MailScanner/etc/spam.assassin.prefs.conf --lint &> sa.rpt

Look in the sa.rpt. I would be looking for the rbl, razor
timeouts and so forth

If all looks well switch get a copy of an email and, and also as
the user that normally runs SA

spamassassin -D -p /opt/MailScanner/etc/spam.assassin.prefs.conf
< EMAILFILENAME &> sa.rpt

and look at the output. It will give you line by line out of what
SA is doing and what the results are. I recently lowered my razor
timeout because they were getting a bit flakey now and then and
razor, dcc, pyzor and rbl time outs in spam.assassin.prefs.conf
should all be around 5 (especially if you are running a caching
name service)



>
> --
> Martin Hepworth
> Snr Systems Administrator
> Solid State Logic
> Tel: +44 (0)1865 842300
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> MailScanner thanks transtec Computers for their support.
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>