https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6335
--- Comment #25 from Paul Fisher <[email protected]> 2010-03-02 20:08:48 UTC --- (In reply to comment #23) > Sure enough, we are geting 127.0.1.255 "IP queries prohibited!" most of the > time: Even after the issue causing this particular problem is fixed, as a general protection against SpamAssassin accidentally sending data that the DBL thinks is an IP address (correctly or otherwise), URIBL_DBL should never fire if the DBL returns 127.0.1.255. Since the DBL is fundamentally represented as a dnset via rbldnsd, the DBL's view of what is and is not an IP address is not perfect. For example, the DBL thinks that "example.com.1" is an IP address. $ host example.com.1.dbl.spamhaus.org example.com.1.dbl.spamhaus.org has address 127.0.1.255 For our local Exim MTA-level/DBL integration that we're using in production at Berkeley, we make sure we have a sane looking TLD before sending a query off to the DBL, and additionally, we ignore any 127.0.1.255 return codes. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
