Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: whitelist_from doesn't work. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176902 ------- Additional Comments From jm@xxxxxxxxxx 2006-01-04 19:02 EST ------- something else is up. : exit=0 Wed Jan 4 15:59:43 PST 2006; cd /home/jm/ftp/sa/b3_1_0 : jm 24...; cp ~/DL/user_prefs ~/.spamassassin/user_prefs : exit=0 Wed Jan 4 15:59:50 PST 2006; cd /home/jm/ftp/sa/b3_1_0 : jm 25...; ./spamassassin -D -t < ~/DL/davem >o 2>o2 : exit=0 Wed Jan 4 16:00:14 PST 2006; cd /home/jm/ftp/sa/b3_1_0 : jm 26...; grep WHITELIST o X-Spam-Status: No, score=-100.0 required=5.0 tests=USER_IN_WHITELIST -100 USER_IN_WHITELIST From: address is in the user's white-list : exit=0 Wed Jan 4 16:00:17 PST 2006; cd /home/jm/ftp/sa/b3_1_0 : jm 27...; in other words, a command-line invocation of the "spamassassin" script with that user_prefs file, fired the USER_IN_WHITELIST rule just fine. Possibilities I've seen before in this situation: 1. are you using "spamd"? or amavisd, MailScanner, or other app that uses the SA perl modules directly? those latter apps all implement their own, separate whitelisting systems. 2. could it be that the spamd server cannot read the user_prefs for some reason, possibly because it's using a spamd command-line switch that causes it to setuid to another uid ("-u") before it reads that user_prefs? it might be worth posting the spamd command-line switches in use. (/etc/sysconfig/spamassassin iirc) I think it's most likely #2, which matches what Sidney's thinking, too. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
