Help! SA timing out, mail undelivered

[Furnish, Trever G]

This is the first time I've looked at ms/sa debug output, so maybe this is a
red herring (especially since you say rbl's seem to be working), but why
does it seem to think dns is unavailable?

Also, I'm a little confused about why a SA timeout that MS properly kills
would be responsible for stopped mail-flow - when I see messages like that,
I still get the message delivered, just not scanned by SA.  ...at least I
think I still get it.  Maybe I need to verify that. :-)

When you say "disable SA" you mean setting "use spamassassin = no" in the
MailScanner.conf file, right?

-t.


> -----Original Message-----
> From: mikea [mailto:mikea at MIKEA.ATH.CX]
> Sent: Tuesday, August 05, 2003 3:34 PM
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: Help! SA timing out, mail undelivered
> Meanwhile, SA is timing out:
>
[...snip...]
> Aug  5 15:23:23 isdmon2 MailScanner[34303]: SpamAssassin
> timed out and was killed, consecutive failure 1 of 20
> Aug  5 15:23:37 isdmon2 MailScanner[34312]: SpamAssassin
> timed out and was killed, consecutive failure 1 of 20
> Aug  5 15:23:52 isdmon2 MailScanner[34353]: SpamAssassin
> timed out and was killed, consecutive failure 1 of 20
> Aug  5 15:24:09 isdmon2 MailScanner[34391]: SpamAssassin
> timed out and was killed, consecutive failure 1 of 20
> Aug  5 15:24:21 isdmon2 MailScanner[34397]: SpamAssassin
> timed out and was killed, consecutive failure 1 of 20
> Aug  5 15:26:09 isdmon2 MailScanner[34740]: SpamAssassin
> timed out and was killed, consecutive failure 1 of 20
>
> Suggestions?
>
> --
> Mike Andrews
> mikea at mikea.ath.cx
> Tired old sysadmin since 1964
>