Okay, I’m keeping an eye on things, but it looks like specifically defining the auto expire in the local.cf might have helped.  I’ll keep an eye on it and let everyone know.  If it does end up fixing things I’ll post a bug report asking that it be a default option for the next package release.

 

Justice London

 


From: Jake Vickers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 10:49 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] SA bayes database issues

 

Justice London wrote:

The permissions are set when the files are created.  Directory/file permissions are:

 

drwx------   2 vpopmail vchkpw   61 Aug 23 10:33 .

drwxr-xr-x  12 vpopmail vchkpw 4.0K Aug  9 08:27 ..

-rw-------   1 vpopmail vchkpw  40M Aug 23 10:33 auto-whitelist

-rw-------   1 vpopmail vchkpw 160K Aug 23 10:33 bayes_seen

-rw-------   1 vpopmail vchkpw 5.0M Aug 23 10:33 bayes_toks

 

Same here. Okay, wanted to make sure. I have not run into this problem, but I'm probably also defining a few more config variables than you are:

<---snip--->
use_bayes 1
bayes_file_mode 0700
#bayes_path /root/.spamassassin/bayes
bayes_path /etc/mail/spamassassin/.spamassassin/bayes
bayes_auto_learn_threshold_spam 8.0
bayes_auto_expire 1
#use_dcc 1
use_auto_whitelist 1
auto_whitelist_file_mode 0700
#auto_whitelist_path /root/.spamassassin/auto-whitelist
auto_whitelist_path /etc/mail/spamassassin/.spamassassin/auto-whitelist
<---snip--->

Reply via email to