Do you have Bayes autolearn enabled, or are you using the trainable form of Bayes? If so, check the /var/log/spamd/current log and look for these entries:
cannot open bayes databases /var/spool/spamd/.spamassassin/bayes_* R/W: tie failed: Permission denied
or (from another server):
cannot open bayes databases /var/spool/spamd/.spamassassin/bayes_* R/W: lock failed: Interrupted system call
For some reason, updates to spamassassin (or possibly other mail updates) changes ownership on one or two of the bayes database files to the wrong value of root, and bayes stops working.
I use these commands to fix it:
chown spamd.spamd /var/spool/spamd/.spamassassin/bayes_*
And sometimes I have to:
chmod 750 /var/spool/spamd/.spamassassin/bayes_*
You can look at current permissions and ownership and make only the needed changes if you want...
Not all of the bayes_* files are altered, but at least one is with certain updates, which is enough to break Bayes filtering...
I'd like to collect a list of problems that can occur in the spamd log and write a program to hunt for them, and possibly correct them. In the past, there werent so many updates, so it was easy to do manually. But since the 7.2 update, there have been a lot of little updates, and I've had to watch the logs more closely...
7 Replies
1805 Views