Re: Bayes R/W lock failed > If it's sporadic, that's not a problem. SA tried to get a read-write 
> lock on the bayes DB, presumably for autolearning or autoexpiry, but 
> some other SA instance may have had it.
> 
> Rather than block your mail queue, SA gave up.
> 
> This is only a problem if it happens *every* time SA tries to
> autolearn, in which case your rights aren't set up to allow writing
> of the files, only reading.

When the bayes.lock is created it remains ever, I must delete it
manually and then restart "/etc/init.d/spamd restart".

Before "spamd restart" if I type "netstat -at" I see a lot of spamd
connections.

My dir: /home/spamassassin/.spamassassin
-rw-------  1 spamd spamd 40169472 Feb 28 15:45 auto-whitelist
-rw-------  1 spamd spamd   339832 Feb 28 15:45 bayes_journal
-rw-------  1 spamd spamd 10510336 Feb 28 11:53 bayes_seen
-rw-------  1 spamd spamd 83533824 Feb 28 11:53 bayes_toks

Maybe the file dimensions are too big or whatelse?

> no. That would be caused by a timeout or over-sized message that
> didn't get scanned.

Where I can check the size and timeout of a message?

--
Massimiliano Marini - http://www.linuxtime.it/massimilianomarini/
"It's easier to invent the future than to predict it."  -- Alan Kay


