Re: strange auto-whitelist behavior

2005-12-22 Thread Marcus Sobchak
Am Freitag, den 23.12.2005, 01:02 +0100 schrieb Marcus Sobchak:

> today I've upgraded from 3.0.4 to 3.1.0 (on debian). Spam detection
> works fine, but from time to time I have these errors in my mail.log:
> 
> 
> Dec 22 23:44:23 walter spamd[8985]: auto-whitelist: open of
> auto-whitelist file failed: locker: safe_lock: cannot create tmp
> lockfile 
> /var/spool/uucp/.spamassassin/auto-whitelist.lock.walter.domain.de.8985 for 
> /var/spool/uucp/.spamassassin/auto-whitelist.lock: No such file or directory
> 
> Dec 22 23:54:27 walter spamd[8985]: auto-whitelist: open of
> auto-whitelist file failed: locker: safe_lock: cannot create tmp
> lockfile 
> /var/www/user01/.spamassassin/auto-whitelist.lock.walter.domain.de.8985 for 
> /var/www/user01/.spamassassin/auto-whitelist.lock: No such file or directory
> 
> 
> spamd is running as root and forking its children as user spamd. The
> autowhitelisting should by system wide, not by user. Spamd should try to
> finde the awl file in  /var/spool/spamd/.spamassassin.
> 
> Spamd is started as daemon with these options:
>  
>   OPTIONS="--username=spamd --max-children 10
> --helper-home-dir=/var/spool/spamd"
> 
> local.cf is Debian's standard local.cf


Just read about the --nouser-config option, but not sure, if it has
something to do with my problem.

Cheers,
Marcus




strange auto-whitelist behavior

2005-12-22 Thread Marcus Sobchak
Hi,

today I've upgraded from 3.0.4 to 3.1.0 (on debian). Spam detection
works fine, but from time to time I have these errors in my mail.log:


Dec 22 23:44:23 walter spamd[8985]: auto-whitelist: open of
auto-whitelist file failed: locker: safe_lock: cannot create tmp
lockfile 
/var/spool/uucp/.spamassassin/auto-whitelist.lock.walter.domain.de.8985 for 
/var/spool/uucp/.spamassassin/auto-whitelist.lock: No such file or directory

Dec 22 23:54:27 walter spamd[8985]: auto-whitelist: open of
auto-whitelist file failed: locker: safe_lock: cannot create tmp
lockfile 
/var/www/user01/.spamassassin/auto-whitelist.lock.walter.domain.de.8985 for 
/var/www/user01/.spamassassin/auto-whitelist.lock: No such file or directory


spamd is running as root and forking its children as user spamd. The
autowhitelisting should by system wide, not by user. Spamd should try to
finde the awl file in  /var/spool/spamd/.spamassassin.

Spamd is started as daemon with these options:
 
  OPTIONS="--username=spamd --max-children 10
--helper-home-dir=/var/spool/spamd"

local.cf is Debian's standard local.cf

Any ideas what is going wrong here?

Thanks,
Marcus