http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4938
Summary: Tries to update auto-whitelist for wrong user
Product: Spamassassin
Version: unspecified
Platform: Other
URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=360984
OS/Version: other
Status: NEW
Severity: normal
Priority: P5
Component: spamc/spamd
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
Package: spamassassin
Version: 3.1.0a-2
Severity: normal
Hi,
I run spamassassin with the following command line:
spamd -c -H -m 2 -i 0.0.0.0 -A some-ips --syslog-socket=unix
Both local and remote users use spamc -f in their .procmailrc to have their
mail filtered. auto-whitelisting is turned on.
Sometimes (often), the following happens:
2006-03-24 03:31:30.188563500 [13731] info: spamd: connection from remoteclient
[192.168.0.15] at port 49250
2006-03-24 03:31:36.071642500 [13731] info: spamd: handle_user unable to find
user: remoteuser
2006-03-24 03:31:36.649337500 [13731] warn: spamd: still running as root: user
not specified with -u, not found, or set to root, falling back to nobody at
/usr/sbin/spamd line 1150, <GEN662> line 4.
2006-03-24 03:31:43.034921500 [13731] info: spamd: processing message
<message_id> for remoteuser:65534
2006-03-24 03:32:35.643921500 [13731] error: locker: safe_lock: cannot create
lockfile /home/localuser/.spamassassin/auto-whitelist.mutex: Permission denied
2006-03-24 03:32:35.694168500 [13731] warn: auto-whitelist: open of
auto-whitelist file failed: locker: safe_lock: cannot create lockfile
/home/localuser/.spamassassin/auto-whitelist.mutex: Permission denied
2006-03-24 03:32:35.765700500 [13731] error: Can't call method "finish" on an
undefined value at /usr/share/perl5/Mail/SpamAssassin/Plugin/AWL.pm line 397.
2006-03-24 03:32:36.920501500 [13731] info: spamd: clean message (0.0/5.0) for
elan:65534 in 67.3 seconds, 4017 bytes.
2006-03-24 03:32:36.932078500 [13731] info: spamd: result: . 0 -
scantime=67.3,size=4017,user=remoteuser,uid=65534,required_score=5.0,rhost=remoteclient,raddr=192.168.0.15,rport=49250,mid=<message_id>,autolearn=no
The username of remoteuser doesn't exist locally, so spamd is right in
falling back to nobody. However, it shouldn't try to fiddle with the
auto-whitelist settings of localuser (incidentally, one of the local users
who also use spamc -f).
Could it be that spamd somehow unintentionally remembers the location of the
last auto-whitelist file it updated, and only changes this value if the
specified local username exists, but not on falling back to the nobody user?
Andras
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
