On Sunday 07 Mar 2004 17:58, Chris wrote: > While looking through my syslog I found the following entry: > > Mar 7 04:20:47 dhcppc0 spamd[24012]: bayes: lock: 24012 cannot create tmp > lockfile /etc/mail/spamassassin/bayes.lock.dhcppc0.24012 for > /etc/mail/spamassassin/bayes.lock: Permission denied > > I'm assuming from the line below, I have thousands of these, that SA writes > an entry for each rule it runs against a message? > > Mar 7 06:10:43 dhcppc0 spamd[1785]: Subroutine > RM_usd_onllovetodate_uri_test redefined at > /etc/mail/spamassassin/1_myrule.cf, rule RM_usd_onllovetodate, line 8, > <GEN69> line 35. > Mar 7 06:10:43 dhcppc0 spamd[1785]: Subroutine WLS_URI_7258_uri_test > redefined at > /etc/mail/spamassassin/sa-blacklist.2004022204.withdead.uri.cf, rule > WLS_URI_7258, line 8, <GEN69> line 35. > > And lastly, probably a dumb newbie question, there is no problems caused if > I deleted all the .gzip log files in /var/log is there? > > Thanks > Chris
It looks like you are using spamassassin "site wide" with everyone using the same settings. I say this because if your users had a ~/.spamassassin/user_prefs file then by default it would try to use a lock file in that folder. Your system is trying to use a lock file in the site wide settings folder /etc/mail/spamassassin which of course does not have write permission for users. The solution is to either put the line bayes_path /path/to/file in the /etc/mail/spamassassin/local.cf file where the path points to a directory with 666 permissions, or else create a ~/.spamassassin/user_prefs file in each users home. The advantage of doing this is that each user will have customised spamassassin settings and their own Bayes database. Refer to the Postfix guide on my home page for suggestions of how to set it up. derek -- www.jennings.homelinux.net http://twiki.mdklinuxfaq.org
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
