Bayeslockerror

SpamAssassin reports "R/O: tie failed: Permission denied" in sendlog

This is how SpamAssassin was designed and does not mean something is broken on your Toaster. You'll likely only see this error when you have a site-wide bayesian database.

From SpamAssassin's mailing list:

Occasional lock failures for the R/W lock are perfectly normal in SA, and 
actually somewhat common on busy servers. However, they shouldn't happen if 
you've only got one instance of spamc running at the time.

SA acquires the R/W lock when it wants to do any of the "opportunistic" 
operations, ones involving autolearning and bayes housekeeping. However, 
it's safe for these operations to fail.

So, if SA decides to autolearn a message, but another SA instance is 
already autolearning, or expiring tokens, it will fail the get the R/W 
lock. The alternative is for SA to wait, which slows down mail processing. 
It's much better to simply skip the autolearning and move on to delivering 
the message.