https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6552
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |software+spamassassin@kd6lv | |w.ampr.org --- Comment #19 from [email protected] 2011-04-06 14:59:22 EDT --- Do we really need this ruleset as is? Cymru.com maintains a DNSBL of bogons. Yes, I am aware that the current implementation does no DNS lookup while accessing a DNSBL ovbiously does, but why maintain the same info in different forms. Using the DNSBL means no further maintenance on SA's part, especially when the "fullbogons" list is used (as opposed to the simpler list). Actually, I prefer to check for such martians in the MTA itself (sendmail, by using the DNSBL, with an access table check occuring beforehand to exempt any local usage of private addresses), but that will only check the incoming address. In such a configuration, this rule would never fire -- as SA would never see incoming mail from such an address. The MTA (or even the firewall) would deny the connection way before SA is queried about any such message. I know that not everyone will configure their systems as I do. However, I do question its usefulness. I do note that this may detect the targeted bad IPs from prior connections in the trace chain, but still to hard code such (which should also happen rarely) may not be the way to go. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
