Hi,
Check your spamassassin bayes directory, in your case it's
/home/spamassassin/.spamassassin/, for the bayes.lock.* files? I seen
this you need to temporarily stop spamd then remove the bayes.lock.*
files there. Then start spamd and it should clear this up.
I think the reason for this if you stop spamd and there is
bayes.lock.* there, and there shouldn't when it is stopped, when you
start up and spamd needs to create a bayes.lock.* it get confused
because there are another one existing and complains to you in the
log.
I hope this helps.
Frank
Debian - SA 3.2.4
In my log I'found a lot message like this:
Feb 28 05:42:32 server spamd[9351]: bayes: cannot open bayes
databases /home/spamassassin/.spamassassin/bayes_* R/W: lock failed:
File exists
How can I solve this problem?
local.cf
rewrite_header Subject *****SPAM*****
report_safe 0
required_score 4
use_bayes 1
bayes_auto_learn 1
bayes_auto_expire 0
bayes_learn_to_journal 1
bayes_journal_max_size 0
Could (lock failed) be the cause of:
X-Spam-Status: No, hits=? required=?
--
Massimiliano Marini - http://www.linuxtime.it/massimilianomarini/
"It's easier to invent the future than to predict it." -- Alan Kay
