On man 14 sep 2009 15:46:22 CEST, Mark Martinec wrote
Benny, I very much agree with you, the /16 is too wide, and I've
seen cases where good and bad sites share the same /16 address range.
is the dkim awl not solveing it in 3.3 ?
why is spf not added ?
Would you please open a problem report on this. Perhaps there's
still time to get it to a 3.3.
i created a patch to 3.2.5
diff -urp
sa/Mail-SpamAssassin-3.2.5/lib/Mail/SpamAssassin/AutoWhitelist.pm
sa-patch/Mail-SpamAssassin-3.2.5/lib/Mail/SpamAssassin/AutoWhitelist.pm
---
sa/Mail-SpamAssassin-3.2.5/lib/Mail/SpamAssassin/AutoWhitelist.pm 2008-06-10
11:20:22.000000000 +0200
+++
sa-patch/Mail-SpamAssassin-3.2.5/lib/Mail/SpamAssassin/AutoWhitelist.pm 2009-09-14 23:36:51.000000000
+0200
@@ -271,7 +271,9 @@ sub pack_addr {
# the user running "add-addr-to-*".
$origip = 'none';
} else {
- $origip =~ s/\.\d{1,3}\.\d{1,3}$//gs;
+ # patch 3.2.5 to use /24 where default is /16
+ # $origip =~ s/\.\d{1,3}\.\d{1,3}$//gs;
+ $origip =~ s/\.\d{1,3}\.\d{1,3}\.\d{1,3}$//gs;
}
$origip =~ s/[^0-9\.noe]/_/gs; # paranoia
warning i dont know perl to be sure its working :)
hope this is all that is needed to change the hardcoded /16 to hardcoded /24
--
xpoint
