SA Timed Out (Redux)

Chris Trudeau chris at
Sat Oct 11 03:49:42 IST 2003


SpamAssassin Timeout = 40

Using DCC/Razor and RBL checks...any ideas on how to determine if these
are timing out?  Its weird that in batches of multiple emails...only one
message will result in the timed out message...

Any ideas about that?  FWIW...I have a MailScanner 4.23/SA 2.55 machine
right next to it...on the SAME pipe...that is not experiencing these
problems...identical configurations...


P.S.  I would rather messages that timeout...then get re-queued...and
re-scanned...seems to me that a default timed out resulting in delivery
would present an avenue for a DOS against SA...SPAMMERS could
say...hmmm...all we have to do it cause SA to timeout...and everyone
using it...would DELIVER our messages....hmmmm.....I could be and am
likely wrong...

-----Original Message-----
From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK] On
Behalf Of Kevin Spicer
Sent: Friday, October 10, 2003 6:24 PM
Subject: Re: SA Timed Out (Redux)

On Fri, 2003-10-10 at 23:08, Chris Trudeau wrote:

> Is it safe to assume that if SA times out, mailscanner delivers?  Why
> that be?

Because its better to deliver some spam than to stop delivering mail or
dump legitimate mail.

Odds are the problem is network checks timing out.  Review the RBL
checks its using, check DCC/ Pyzor/ Razor are working if you use them.

Also check that SpamAssassin Timeout = 40 in MailScanner.conf

BMRB International
+44 (0)20 8566 5000
This message (and any attachment) is intended only for the
recipient and may contain confidential and/or privileged
material.  If you have received this in error, please contact the
sender and delete this message immediately.  Disclosure, copying
or other action taken in respect of this email or in
reliance on it is prohibited.  BMRB International Limited
accepts no liability in relation to any personal emails, or
content of any email which does not directly relate to our

More information about the MailScanner mailing list