I am at my wits end regarding this issue. I am getting very frequent:
May 14 09:58:05 citlatepetl spamd[5125]: Cannot open bayes databases /home/spam-filter/etc/mail/spamassassin/bayes_* R/W: lock failed: File exists
messages. From what I have googled I have done just about everything I could find regarding this issue. As I have a site wide Bayes database I have the following lines in my /etc/mail/spamassassin/local.cf:
bayes_auto_expire 0 bayes_learn_to_journal 1 bayes_file_mode 0777
I have limited the number of spamd instances via:
daemon /home/spam-filter/bin/spamd -d -c -m 5 --max-conn-per-child=10 -p 783 -H /home/spam-filter/razor --user-config --virtual-config-dir=/home/sites/%d/users/%u
The host server is RaQ550 with 2GB SDRAM so memory shouldn't be an issue. The directory protections for the database are:
[root etc]# ls -alt /home/spam-filter/etc/mail total 4 drwxrwxrwx 2 root root 4096 May 14 10:04 spamassassin
The file protections are:
-rw-rw-rw- 1 prganci users 165988 May 14 10:05 bayes_journal -rw------- 1 pangione users 34 May 14 10:00 bayes.lock -rw-rw-rw- 1 hubbard users 136548 May 14 09:58 bayes_journal.old -rw-rw-rw- 1 root root 5279744 May 14 09:38 bayes_toks -rw-rw-rw- 1 root root 5226496 May 9 20:23 bayes_seen
Please note that I always start off with bayes.lock with -rw-rw-rw- so it is spamd/spamc which is changing the owner/protection on the lock file. The /etc/procmailrc file looks like:
DROPPRIVS=yes SHELL=/bin/sh #LOGFILE=/var/log/procmail.log #VERBOSE=on TIMEOUT=60 :0fw: * < 200000 |/home/spam-filter/bin/spamc -p 783 -u $1 -t 120 # # Drop high scoring spam into bit bucket. :0: * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\* /home/sites/magnoliaroad.net/users/definitespam/mail/saved-messages
# Work around procmail bug: any output on stderr will cause the "F" in "From"
# to be dropped. This will re-add it.
# NOTE: This is probably NOT needed in recent versions of procmail
:0
* ^^rom[ ]
{
LOG="*** Dropped F off From_ header! Fixing up. "
:0 fhw | sed -e '1s/^/F/' }
Does anybody have any idea how I cure this problem. About the only thing I haven't attempted is moving from a global Bayes db to a local user Bayes db.
Thank you for any suggestions you might have.
-- Paul ([EMAIL PROTECTED])
