https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6724
--- Comment #32 from Matthias Leisi <[email protected]> 2011-12-19 16:08:21 UTC --- (In reply to comment #31) > > This should avoid any unnecessary queries and limit collateral damage. > > Neat! There will be some finetuning necessary, as I see some resolvers being unhappy about the .invalid nameserver (doing three retries; I'll try out some variations over the next couple of days to assess impact & avoid collateral damage). > As the commit is already done checking for 127.0.X.255, this is a simple IP > address change handled by sa-update AND we are already using another 127 bit > for URIBL, I see no reason to hold things up based on Comment 11 at this > time. > > If you can implement this with 127.0.0.255, then the blocked rule is already > live and I can then turn back on the scoring for DNSWL. Some are already receiving 127.0.0.255 (those asking the parent-zone nameservers directly), others will start to get them as soon as I switch it on (sometime tonight, I'm currently on the road). -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
