https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6728
D. Stussy <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |software+spamassassin@kd6lv | |w.ampr.org --- Comment #7 from D. Stussy <[email protected]> 2011-12-15 23:21:55 UTC --- In my opinion, "blocked" should ALSO trigger upon the affirmative receiving of an A record OUTSIDE of 127.0.0.0/8, regardless of ruleset processing. This part of the recognition would be performed in the routine which processes DNS-list results. "Blocked" detection for this purpose should be a boolean flag - to handle a case where more than one offending address is received, and handled after such processing. That way, we won't accidentally bump the timeout counter more than once when retrying. Functional DNS lists should explicitly return "0.0.0.0" (i.e. no rule is necessary to detect them). Non-functional lists may return any [unicast] address as they may be "parked" at a registration service for sale and SA got the A record (via a DNS wildcard entry) meant for HTTP redirection to a "domain for sale" web server page. This is in addition to the rule detection proposed in "comment 0." -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
