Spam assassin timeouts

[Glenn Steen]

2008/12/10 vinayan KP <mailwatch.kp at gmail.com>:
> Dear Ram,
>
> Thank you very much for your mail.  I learned linux just recently I am
> not an expert.  I normally used to try things whenever I get time but
> now I hardly have any time these days to sit and feel dont have enough
> knowledge to fix this problem.  A third party installed and configured
> mailscanner for us couple of years back but that company does not
> exist anymore. Hope you would be able to help me out.
>
> The following are the size of bayes file.  Are thse alright? The
> bayes_seen file is too large but it was like this for a long time and
> was working alright.
>
> -rw-------  1 root root 9.4K Dec 10 14:29 bayes_journal
> -rw-rw-rw-  1 root root 5.7K Dec 10 14:29 bayes.mutex
> -rw-------  1 root root 167M Dec 10 14:26 bayes_seen
> -rw-------  1 root root 9.7M Dec 10 14:28 bayes_toks
> -rw-------  1 root root  12K Dec  9 10:35 bayes_toks.expire10686
> -rw-------  1 root root  12K Dec 10 00:12 bayes_toks.expire11495
> -rw-------  1 root root  12K Dec  8 19:22 bayes_toks.expire11824
> -rw-------  1 root root  12K Dec  8 20:40 bayes_toks.expire13768
> -rw-------  1 root root  12K Dec 10 07:48 bayes_toks.expire28490
> -rw-------  1 root root  12K Dec  7 21:22 bayes_toks.expire31832
> -rw-------  1 root root    0 Dec  2 04:04 __db.bayes_toks.expire12682
> -rw-------  1 root root  12K Nov 27 18:58 __db.bayes_toks.expire14247
> -rw-------  1 root root  12K Sep  6 06:22 __db.bayes_toks.expire15605
> -rw-------  1 root root  12K Nov 14 14:38 __db.bayes_toks.expire15684
> -rw-------  1 root root 4.0K Sep  2 07:48 __db.bayes_toks.expire1745
> -rw-------  1 root root  12K Dec  2 08:39 __db.bayes_toks.expire20880
> -rw-------  1 root root  12K Dec  6 00:18 __db.bayes_toks.expire23304
> -rw-------  1 root root    0 Dec  4 16:39 __db.bayes_toks.expire23851
> -rw-------  1 root root    0 Oct 26 19:52 __db.bayes_toks.expire24361
> -rw-------  1 root root    0 Sep  2 04:52 __db.bayes_toks.expire29096
> -rw-------  1 root root  12K Nov 11 17:37 __db.bayes_toks.expire30758
> -rw-------  1 root root  12K Oct 23 18:31 __db.bayes_toks.expire31745
> -rw-------  1 root root 4.0K Dec  9 05:28 __db.bayes_toks.expire32018
> -rw-------  1 root root    0 Nov 21 04:07 __db.bayes_toks.expire32087
> -rw-------  1 root root  12K Dec  5 15:17 __db.bayes_toks.expire3656
> -rw-------  1 root root    0 Dec  4 05:45 __db.bayes_toks.expire5747
> -rw-------  1 root root  12K Oct 22 16:03 __db.bayes_toks.expire7440
> -rw-------  1 root root  12K Nov 26 16:21 __db.bayes_toks.expire7458
> -rw-------  1 root root    0 Sep 18 00:39 __db.bayes_toks.expire9575
> -rw-r--r--  1 root root 1.5K Dec  8 13:23 user_prefs
>
(snip)
This is classic... You have a huge seen file there, and a load of
expire files from unsuccessful expire runs. Remove the seen file as
well as all the expire files, then do a manual expire... Consider
configuring your bayes for manual expire only. Also consider
increasing the SA timeout value rather much ... in MailScanner.conf.
MS will rudely cut off some SA operations otherwise. Exactly what you
need, as well as where depend on your circumstances, so I'll refrain
from giving any hard numbers.
Removing the bayes_seen file will affect your ability to unlearn
messages previously learnt, but ... that is likely something you can
live with temporarily.

As Ram says, this has been covered numerous times (and all the other
reasons for SA to time out:-) on this list... and I'm almost certain
you can find pertinent information in the wiki/maq as well.

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se