spamassassin timeouts question

Julian Field mailscanner at
Tue Jan 6 17:34:29 GMT 2004

At 17:30 06/01/2004, you wrote:
>I don’t understand how this can happen with a message

>X-MailScanner-SpamCheck: not spam, SpamAssassin (timed out)
>When the configuration is so

>Max SpamAssassin Timeouts = 10
>And the only log message I see is
>Jan  6 09:10:43 defender MailScanner[11056]: SpamAssassin timed out and 
>was killed, consecutive failure 1 of 10
>I am not seeing failure 2 of 10 and so on

It is succeeding some times and failing other times. It needs to hit 10 
consecutive timeouts before SpamAssassin network checks are disabled. 20 
consecutive timeouts (including the above 10) will cause SpamAssassin to be 
disabled altogether. Even if it keeps failing, it's usually due to network 
checks which is why the behaviour is slightly cleverer than the simple 
configuration option suggests.
Julian Field
Professional Support Services at
MailScanner thanks transtec Computers for their support
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

More information about the MailScanner mailing list