On 19 Dec 2003, at 22:15, Lukreme wrote:I set the permissions on all the bayes files to 700 for all users and I still ended up having them get switched to --------- after some period of time. Although, it appears that this time it was a couple of hours:
One more datum, this does not happen only on my list account. It happens on all accounts, eventually. It's just my list account is by far the highest volume account that is using bayes. For example, this morning I had to set 4 accounts back to 0700 permissions on the bayes_journal file. There are many accounts that have bayes_toks and bayes_seen and have no bayes_journals.
Ok, even more info. Out of the 20-30 accounts that have spamassassin running from their procmailrcs, only 4 have bayes_journal files. If I delete those files, the are recreated with --------- perms. If I change the perms, they are eventually changed back to ---------. the only bayes settings in local.cf are:
$ grep bayes /etc/mail/spamassassin/local.cf
bayes_file_mode 0770 # have tried 0700, 0644, and 0666 with identical results
bayes_path /etc/mail/spamassassin/bayes # recently added
bayes_expiry_max_db_size 150000 # recently added
bayes_journal_max_size 102400 # recently added
bayes_auto_learn_threshold_nonspam 0.1
bayes_auto_learn_threshold_spam 9.0
bayes_auto_learn 1
$ ls -lstr /etc/mail/spamassassin/ total 24 22 -rw-r--r-- 1 root wheel 21747 Dec 21 15:26 local.cf 2 drwxrwxrwx 2 root wheel 512 Dec 21 15:27 bayes
--
Though it's cold and lonely in the deep dark night I can see paradise by the dashboard light.
smime.p7s
Description: S/MIME cryptographic signature
