Unusual # of MailScanner processes running

[Peter Bonivart]

Jason Burzenski wrote:
> Update 2004-04-03. Julian included a patch in MS 4.29.7 which fixes the
> problem
> until SA is fixed. Users of MS 4.29.7 and later are recommended to expire
> tokens from there instead.
>
> How do I expire tokens from MS 4.29.7?

I wrote that FAQ entry and I have used that method for over three months
without a single problem. I updated it since some have reported success
with the newest stable release of MS (the problem is really in SA).

If you want to do it from MS use this in MailScanner.conf:

# If you are using the Bayesian statistics engine on a busy server,
# you may well need to force a Bayesian database rebuild and expiry
# at regular intervals. This is measures in seconds.
# 1 day = 86400 seconds.
# To disable this feature set this to 0.
Rebuild Bayes Every = 0


# The Bayesian database rebuild and expiry may take a 2 or 3 minutes
# to complete. During this time you can either wait, or simply
# disable SpamAssassin checks until it has completed.
Wait During Bayes Rebuild = no

Also remember to uncomment this in spam.assassin.prefs.conf:

# MailScanner: When using the scheduled Bayes expiry feature, you probably
# MailScanner: want to turn off auto-expiry as it will rarely complete
before
# MailScanner: it is killed for taking too long. You will just end up with
# MailScanner: big bayes_toks.new files wasting space.
# bayes_auto_expire 0

--
/Peter Bonivart

--Unix lovers do it in the Sun

Sun Fire V210, Solaris 9, Sendmail 8.12.10, MailScanner 4.29.7,
SpamAssassin 2.63 + DCC 1.2.39, ClamAV 0.70RC + GMP 4.1.2, Vispan 1.3