https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6460
--- Comment #11 from Kevin A. McGrail <[email protected]> 2010-11-30 18:31:45 UTC --- (In reply to comment #10) > Created an attachment (id=4828) --> (https://issues.apache.org/SpamAssassin/attachment.cgi?id=4828) [details] > Remove newly allocated and to-be-allocated IANA address ranges from the rule > > As it turns out, even now the rule triggers on several newly-allocated > address ranges, causing false positives. > > The patch strips off all already allocated and to-be-allocated > address ranges from the rule, leaving only the: > - 0.0.0.0/8 self-identification network > - multicast addresses > - all three 'test' networks AXB's comment was +1 for private use networks which doesn't make sense to me since theoretically those should always be trusted, yes? Since your rule doesn't hit 192.168.X or 10.X, I think you covered what makes sense to me. +1 KAM -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
