Editing dbl_allowed
Help Page
|
Text Formatting Rules
|
HTML Basics
This check is superceded by siq_network_allowed, which contains only listings authorized by the IP space delegate, IP space authority or entity with reverse delegation. As IP authorities assert control listings for their IPs, any listings for those IPs in dbl_allowed data will be deleted. Since the dbl_allowed check uses BOTH the authorized listings and guesses (see below) - eventually in an ideal world, the dbl_allowed check and siq_network_allowed check will have identical results. This is an experimental check which contains unverified data. Although we know of ISPs who use this check and are very happy with the results, including using it to reject email they consider to be unauthorized, we strongly urge you not to use this check, and not to use it for REJECTING mail. The Outbound Index principles are to use facts, not guesses. This check includes guesses - however reasonable and useful they may be - they are still guesses. Please carefully examine the source of the data being accessed for this check before deciding in what capacity, or if, you want to use this check. We took the zone file from Easynet's Dynablocks the week it shutdown. Dynablocks was a blacklist which sought to only list dynamic IP addresses (dialup, dynamic cable modem, dynamic dsl) which included an IP address which had sent the DynaBlocks operator spam. (We also saved their criteria page and will post it here as well.) DynaBlocks also found and posted many AUPs which stated that no mail server could be run on the dynamic IPs, for many of the ISPs they listed. DynaBlocks also honored remove requests from individuals who were running outbound mail servers on dynamic IP ranges, if that IP had not sent the DynaBlocks operator spam. We processed the DynaBlocks zone file to extract IP address ranges, then checked for matching forward and reverse DNS on the IPs. We used the resulting FQDN list to create wildcard patterns, and stored those patterns in a database. Dynablocks IPs which were listed as OK also were stored in our database and are honored by the dbl_allowed check. IP addresses which did not have matching reverse and forward DNS, and which were disallowed in DynaBlocks, were discarded. **dbl_allowed check logic:** <PRE> Is this IP found in table "netips"? Found and is disallowed - fail Found and is allowed - pass Not found table "netips" - continue Does this IP have matching forward and reverse DNS ("syncdns")? Yes - If the syncdns matches a disallowed pattern in table "patterns" - fail Yes - If the syncdns matches an allowed pattern in table "patterns" - pass No - does not match any pattern in table "patterns" - continue No listing found regarding this IP - continue </PRE>
Optional note: