2500 timeouts a day!

[Max Kipness]

        I had the same problem 2 weeks ago with slightly more timeouts
and my problem was related to bayes database size/corruption.  I went
through the whole debugging things but couldn't catch a timeout
successfully.  I ended up using the bayes starter db from fsl.com as an
immediate replacement for my old, rickety bayes db that was over 150MB.


        You need SA 2.63 to use bayes-starter and I would run in debug
mode first to make sure it sticks (make sure you adjust permissions so
your new .spamassassin dir and files within match your old one).  

        Here is my cmd line: 

        $ cd /root 
        $ service MailScanner stop 
        $ mv .spamassassin spamold 
        $ wget http://www.fsl.com/support/bayes-starter.tar.gz 
        $ tar xvzf bayes-starter.tar.gz 
        $ mv bayes .spamassassin 
        $ cp spamold/user_prefs .spamassassin 
        $ service MailScanner start 

        This completely solved my problem.  I have been processing about
60K msgs per day per MS server with 0 SA timeouts.  I'm not sure if it
will solve your problem but it might be worth a shot.  How large is your
bayes db now?  Do you do any regularly scheduled maintenance on it (via
MS, SA, etc.?). 

        I may give this a try, but I was actually having time outs
before I implemented bayes.

        Thanks,
        Max 




-------------------------- MailScanner list ----------------------
To leave, send    leave mailscanner    to jiscmail at jiscmail.ac.uk
Before posting, please see the Most Asked Questions at
http://www.mailscanner.biz/maq/     and the archives at
http://www.jiscmail.ac.uk/lists/mailscanner.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20040526/dbfb52f2/attachment.html