I'm still not able to figure this out. I can find no reason why SpamAssassin should be trying to create files in anybody's home directory, but I'm still seeing this error logged every time spamd processes a message:

spamd: mkdir /dev/null: File exists at ///Library/Perl/5.8.1/Mail/ SpamAssassin.pm line 1467

I'm running spamd as "spamd -d -x -u nobody", I've commented out AWL from v310.pre, and I set "bayes_auto_learn 0" so that it shouldn't try to create a Bayes database. I have no idea why it keeps complaining about not being able to create a file in /dev/null.

Exim is running as user 'exim', which has no home directory, but this wasn't a problem for SpamAssassin 3.0.4 and I don't know why spamd, which is running as 'nobody', should care what user is connecting to it.

What am I forgetting to disable so that spamd won't try to create a per-user config file?

  - B


Reply via email to