Tried that, and it didn't work. Even with file permissions set to 777, I was seeing these log entries:
Jul 25 12:36:10 vps spamd[28501]: locker: safe_lock: cannot create tmp lockfile /.spamassassin/auto-whitelist.lock.vps.zinski.net.28501 for /.spamassassin/auto-whitelist.lock: Permission denied Jul 25 12:36:10 vps spamd[28501]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile /.spamassassin/auto-whitelist.lock.vps.zinski.net.28501 for /.spamassassin/auto-whitelist.lock: Permission denied And Jul 25 20:02:32 vps spamd[18096]: bayes: locker: safe_lock: cannot create tmp lockfile /.spamassassin/bayes.lock.vps.zinski.net.18096 for /.spamassassin/bayes.lock: Permission denied Jul 25 20:16:45 vps spamd[26594]: bayes: locker: safe_lock: cannot create lockfile /.spamassassin/bayes.mutex: Permission denied The only thing that would work was to chown the files to nobody:nobody (and, yes, I had the directory permissions set to 777 too.) Steve -----Original Message----- From: Thomas Lindell [mailto:[EMAIL PROTECTED] Sent: Thursday, July 27, 2006 2:17 PM To: users@spamassassin.apache.org Subject: RE: exim4 + forwarding + spamassassin You could have just chmoded the directorys and files to 744
