endless respawning with SA enabled

[Julian Field]

What does your maillog say?
Does the user you are using to run MailScanner have a real home directory?
The SpamAssassin init code fails if there isn't a home directory it can
write to. Most commonly a problem when people are using Exim (as they run
as non-root).

At 10:59 11/03/2003, you wrote:
> > I've recently upgraded to mailscanner 4.13, and SA 2.50
> > (patched) now, whenever I enable SA, mailscanner respawns
> > endlessly, without any processing done. works perfectly when
> > disabled. as far as I can tell, it quits sometime in the SA
> > init stage, but I still haven't looked too deeply there.
> >
>
>I noticed a problem similar to this last week and upon
>investigation I found the following settings (in
>spam.assassin.prefs.conf) to help greatly:
>
># Settings taken from
>#
>http://www.jiscmail.ac.uk/cgi-bin/wa.exe?A2=ind0208&L=mailscanner&P=R9717&I=
>-3
># SpamAssassin Performance Tips (isp-list at TULSACONNECT.COM)
>
># By default, spamassassin will change the Content-type: header of
># suspected spam to "text/plain". This is a safety feature. If you
># prefer to leave the Content-type header alone, set this to 0.
>#
>defang_mime 0
>
># By default, SpamAssassin will run RBL checks.  If your ISP already
># does this, set this to 1.
>#
>skip_rbl_checks 1
>
># only check for a valid MX record once
>check_mx_attempts 1
>
>Andy

--
Julian Field
www.MailScanner.info
MailScanner thanks transtec Computers for their support