On Wed, Dec 14, 2005 at 01:39:16PM -0500, Brian Kendig wrote: > Dec 14 13:27:46 www spamd[3654]: mkdir /dev/null: File exists at /// > Library/Perl/5.8.1/Mail/SpamAssassin.pm line 1467 > Dec 14 13:27:46 www spamd[3654]: locker: safe_lock: cannot create > lockfile /dev/null/.spamassassin/auto-whitelist.mutex: Not a directory > scantime=0.6,size=1111,user=exim,uid=-2,required_score=5.0,rhost=localho > > Downgrading to SpamAssassin 3.0.4 solved the problem, but I'd like to > be able to use 3.1.0. I can't figure out what's going wrong here - > anyone have any ideas?
You have a user (exim) with a home directory of /dev/null. So when SA tries to deal with files in exim's home directory, there is no such directory (/dev/null is a file), so SA tries to make a directory and can't. Then later on, files such as the auto-whitelist lock file are attempted to be created, but /dev/null is a file so you can't make other files in it. If you're running spamd for site-wide usage, ie: always as exim, I'd disable per-user configs (remove -c, add -x), and use the respective config options to aim things like bayes, awl, etc, at a site-wide path. Otherwise, you'll either want to stop sending mail through as user exim, or set a real home directory for the account. -- Randomly Generated Tagline: "You don't want me to pick out your brain surgeon. I don't want your brain surgeon picking out my router :)" - [EMAIL PROTECTED]
pgp8ejWjyWhoJ.pgp
Description: PGP signature
