You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Thomas Schlosser <ts...@googlemail.com> on 2006/06/10 20:08:42 UTC

SA 3.1.3: auto-whitelist cannot create files (tmp lock) in /root/.spamassassin

Hi,
after a fresh install on an SUSE 9.3 box i receive the following errors in
/var/log/mail:


Jun 10 20:00:02 homesrv spamd[7041]: mkdir /root/.spamassassin: Keine
Berechtigung at /usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin.pm line
1486
Jun 10 20:00:02 homesrv spamd[7041]: spamd: processing message <
GTUBE1.1010101@example.net> for root:106
Jun 10 20:00:02 homesrv spamd[7041]: mkdir /root/.spamassassin: Keine
Berechtigung at /usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin.pm line
1486
Jun 10 20:00:02 homesrv spamd[7041]: locker: safe_lock: cannot create tmp
lockfile /root/.spamassassin/auto-
whitelist.lock.homesrv.schlosser-ma.de.7041 for /root/.spamassassin/auto-
whitelist.lock: Keine Berechtigung
Jun 10 20:00:02 homesrv spamd[7041]: auto-whitelist: open of auto-whitelist
file failed: locker: safe_lock: cannot create tmp lockfile
/root/.spamassassin/auto-whitelist.lock.homesrv.schlosser-ma.de.7041 for
/root/.spamassassin/auto-whitelist.lock: Keine Berechtigung


My spamd was started with
/usr/bin/spamd --daemonize --username spamfilt --pidfile
/home/spamfilt/spamd.pid --max-children=5

I am not sure if this 3.0 startup is valid for 3.1 as well?
ps says the following
homesrv:/etc/mail/spamassassin # ps -AF | grep -i spam
spamfilt  6837  6784  0   997  1156   0 19:28 pts/0    00:00:00 su spamfilt
spamfilt  6838  6837  0  1053  1644   0 19:28 pts/0    00:00:00 sh
spamfilt  6924  6842  0   997  1156   0 19:44 pts/0    00:00:00 su spamfilt
spamfilt  6925  6924  0  1084  1696   0 19:44 pts/0    00:00:00 sh
root      7040     1  0  7305 25472   0 19:59 ?        00:00:00
/usr/bin/spamd --daemonize --username spamfilt --pidfile
/home/spamfilt/spamd.pid --max-children=5
spamfilt  7041  7040  0  7537 26504   0 19:59 ?        00:00:00 spamd child
spamfilt  7042  7040  0  7305 25476   0 19:59 ?        00:00:00 spamd child
root      7086  6954  0   687   744   0 20:06 pts/0    00:00:00 grep -i spam

So I assume it would be the best to tell SA to go to
/home/spamfilt/.spamassassin instead of /root/.spamassassin.
Where can I set this directory? (THere are so many places for configs, I am
dazzled)
Or what is the solution for this?

Thanks in advance
Thomas

BTW: Where ist the best place to start spamd? Should this be done in t

Re: SA 3.1.3: auto-whitelist cannot create files (tmp lock) in /root/.spamassassin

Posted by Kai Schaetzl <ma...@conactive.com>.
Thomas Schlosser wrote on Sat, 10 Jun 2006 20:08:42 +0200:

> Jun 10 20:00:02 homesrv spamd[7041]: mkdir /root/.spamassassin: 

> My spamd was started with 
> /usr/bin/spamd --daemonize --username spamfilt

This user isn't allowed to write to /root, but you got a mail for root ...
At least that's what I think is happening, I abandoned spamd long ago.
Create the file by running spamassassin --lint under root, might then be 
readible from spamd. Or go to the wiki and search for "site-wide Bayes".

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com