https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5664
--- Comment #2 from Michael Peddemors <[EMAIL PROTECTED]> 2008-04-01 10:48:34 PST --- Try, although not a 'Dynamic' address in the truest sense of the word, addresses at your domain that say static, still do not conform to 'Best Practises' guidelines for email operators, where the domain should reflect the responsible party for the mail server. If there is a mail server at that IP, or behind that IP, then the domain portion should NOT be nnn.nnn.nnn.static.upstreamprovider.com but something like gateway.operator_domain.com or mail.operator_domain.com etc.. So the check for static may still be a legitimate way to weigh the likelihood of the IP address being simple an access point, and a likely location for trojan generated email vs a properly run email server, with a responsible party to report problems to. All Up Stream providers should provide full reverse DNS to parties wishing to run email services. Possibly at the most, the rule should be broken up into two separate rules with different weights, but the recommendations, and the effectiveness of the rule should not be underestimated, whether the naming convention is 'static' or not, it is still an IP address under the responsibility of the upstream provider, and most likely an access point from which trojans, bots can operate. Technically, the term 'dynamic' is incorrect, but aside from the naming of the rule, the principles are still valid. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
