> I've read all three of your posts.. and don't have any suggestions to help > you.. it looks like a bug to me.
OK, I've opened bug #2734 on it... > What really makes me wonder is why the ip=none entry exists at all. > > Have you been doing something like spamassassin --add-addr-to-whitelist? > In that case.. don't, because it appears that the no-ip entry added by this > command will over-ride any and all IP address specific entries. Nope, I haven't. In fact, before I fully understood what was going on, I did a remove-from-whitelist a few times, and it keeps reappearing - both the "good" entry (with ip=none) and the "bad" entry (with an IP address of a spammer). I had assumed that the ip=none was my outbound mail, which, I promise, is spam-free. Justin said that it contains the last public IP address in the headers, which makes sense - my machine is on a private net, so it has no $origip as far as do_awl_tests is concerned. The only non-stock thing I'm doing is adding a few lines to MIMEDefang to enable AWLs; specifically, the following four lines after the Mail::SpamAssassin->new() call: + my $addrlistfactory; + require Mail::SpamAssassin::DBBasedAddrList; + $addrlistfactory = Mail::SpamAssassin::DBBasedAddrList->new(); + $SASpamTester->set_persistent_address_list_factory ($addrlistfactory); I copied these out of the code that runs when you enable AWLs from the command line, but it's possible I did something wrong, or that something's changed in recent SA versions that I didn't migrate. Any thoughts? ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
