Spamassassin timeouts

[Jules Field]

On 23/07/2009 15:31, Jonas A. Larsen wrote:
>
> I actualy traced it down to all the timeouts happening around 05:00.
>
> That is when the mysql backup runs, so I think it must be some some 
> sort of mysql being unavailable while the backup runs.
>
What other cron jobs happen on your system around then? Such as all the 
ones in /etc/cron.daily? (Your /etc/crontab will tell you when those get 
run). It may be that is when the sa-rebuild happens, which is when it 
cleans up the Bayes database and removes all the old tokens from it. 
This makes Bayes unavailable for quite a while. Look for "Bayes" in 
MailScanner.conf and you will find there are some configuration options 
to alter this behaviour.

> I use mysql for both mailwatch and bayes.
>
> However I still believe a retry function for SA timeouts would be nice 
> to have in MS.
>
> Julian: Please add it to wish list J
>
> *From:* mailscanner-bounces at lists.mailscanner.info 
> [mailto:mailscanner-bounces at lists.mailscanner.info] *On Behalf Of 
> *Martin Hepworth
> *Sent:* 23. juli 2009 15:31
> *To:* MailScanner discussion
> *Subject:* Re: Spamassassin timeouts
>
> Hi
>
> normally this is either due to
>
> 1) DNS issues (lots of RBLs - have you got most of them turned off?),
>
> 2) bayes (have you got this running on a faster SDBM database than the 
> default
> http://wiki.mailscanner.info/doku.php?id=documentation:anti_spam:spamassassin:bayes:sdbm&s=bayes 
> <http://wiki.mailscanner.info/doku.php?id=documentation:anti_spam:spamassassin:bayes:sdbm&s=bayes>
>
> 3) or things like DCC/pyzor/razor.
>
> Another thing to check is the SA-timeout value in MailScanner.conf, I 
> normally raise this well above the 75 default to around 300 at least.
>
>
> -- 
> Martin Hepworth
> Oxford, UK
>
> 2009/7/23 Jonas Akrouh Larsen <jonas at techbiz.dk <mailto:jonas at techbiz.dk>>
>
> Hi List
>
> Hope everyone is enjoying the summer.
>
> I got an annoying problem with SA timeouts.
>
> For the past week my sampling shows that out of 51037 mails, 
> spamassassin timed out on 66 of them.
>
> This is not a big percentage obviously, but it bothers me that I have 
> a pretty decent protection scheme setup which lets very few spams through.
>
> I’d actually guess that SA time outs creates as many false positives 
> (as in mails MS thinks are ham) as actual spam slipping through my 
> anti-spam rules.
>
> I was wondering if there was any way to make MS refuse to have SA 
> timeouts (or maybe make it configureable to atleast try the mail again 
> for x number of times before we accept to let the mail pass MS without 
> having been scanned by SA)
>
> I don’t think this is possible with the current version of MS.
>
> Also note that simply increasing the sa timeout isn’t as good a 
> solution as the confirable “rety behavior (in my opinion atleast)
>
> So am I alone in thinking this would be a neat addition to MS, or what 
> do people think/do with sa timeouts in general?
>
> Med venlig hilsen / Best regards
>
> Jonas Akrouh Larsen
>
> TechBiz ApS
>
> Laplandsgade 4, 2. sal
>
> 2300 København S
>
> Office: 7020 0979
>
> Direct: 3336 9974
>
> Mobile: 5120 1096
>
> Fax: 7020 0978
>
> Web: www.techbiz.dk <http://www.techbiz.dk>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info 
> <mailto:mailscanner at lists.mailscanner.info>
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
>

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.