**********
Sep 30 11:51:19 mail1 spamd[21760]: logmsg: Still running as root: user not specified with -u, not found, or set to root. Fall back to nobody.
Sep 30 11:51:19 mail1 spamd[21760]: Still running as root: user not specified with -u,
not found, or set to root. Fall back to nobody.
<snip>
/var/spool/spamassassin.lock.mail1.elettra.trieste.it.21760 for /var/spool/spamassassin.lock: Permission denied
Sep 30 11:51:19 mail1 spamd[21760]: debug: open of AWL file failed: lock: 21760 cannot
create tmp lockfile /var/spool/spamassassin/auto-whitelist.lock.mail1.elettra.trieste.it.21760 for /var/spool/spamassassin/auto-whitelist.lock:
<snip>
At the moment I'm running spamd as root, in the past time, as suggested in the documentation I tried to change the user running the spamd, but nothing changed...
Where's the problem? or what I'm doing wrong?
I'd suggest adding -u root to your spamd command line as a "quick check". This should allow spamd to run as root, without trying to fall back to "nobody".
In essence what's happening is that SA is trying to use /var/spool/spamassassin for it's AWL path, and that's a forced path. However, that path is owned by root, so only root can write to the files there. When SA winds up falling back to nobody, any attempts to write to that directory fail.
What you *REALLY* want to do, is run spamd as a non-root user AND set /var/spool/spamassassin and all the files in it to be owned by that user, not root.
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
