Jake Vickers wrote:
Justice London wrote:
I might be missing something, but I have searched around the web and
several mailing-lists and haven’t found anything definitive on this.
I run a fairly high traffic mail-server. The bayes_toks database
fills up fairly quickly to 80megs (usually it’s starting to do it
about once a day).
From what I can see the database might be trying to auto-expire but
somehow dies while doing so. There are a large number of stalled
lock-files generated and expiry files as well. I’m assuming I could
setup a cron-job to force a (nightly?) expiry via sa-learn, but I
would think spamassassin should be able to handle the auto-expires.
Should I look to decrease the size of the bayes_toks file at which it
auto-expires… anything to modify in the local.cf?
Have you tried setting this in your local.cf? :
*bayes_expiry_max_db_size (default: 150000)*
What should be the maximum size of the Bayes tokens database? When
expiry occurs, the Bayes system will keep either 75% of the maximum
value, or 100,000 tokens, whichever has a larger value. 150,000
tokens is roughly equivalent to a 8Mb database file.
*bayes_auto_expire (default: 1)*
If enabled, the Bayes system will try to automatically expire old
tokens from the database. Auto-expiry occurs when the number of
tokens in the database surpasses the bayes_expiry_max_db_size value.
I'm thinking that the bayes_auto_expire process is somehow broken.
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
