https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6729
Joe Quinn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Joe Quinn <[email protected]> --- This tool should also run a test query through the machine's DNS to see if it will hit URIBL_BLOCKED. This is probably the single most frequently asked question on users@. I suggest querying test.uribl.com.multi.uribl.com (a documented testpoint per http://uribl.com/about.shtml). If it comes up 127.0.0.1, the current setup will be blocked. If it comes up 127.0.0.14, the current setup will most likely not be blocked. For a nicer error message, we can also do a PTR lookup of the nameserver being resolved. If I ran the tool on my home system, it might say: Your current nameserver at router.manufacturer.com (192.168.1.1) will be unable to perform most RBL lookups due to rate limiting. Make sure you are not using a public nameserver, or your ISP's nameserver. Also make sure your current nameserver is not forwarding to one of these. The SpamAssassin project recommends setting up your own local caching nameserver. For information on how to set one up, see https://wiki.apache.org/spamassassin/CachingNameserver -- You are receiving this mail because: You are the assignee for the bug.
