On Thursday, September 9, 2004, 3:57:58 PM, Frank Ellermann wrote:
Jeff Chan wrote:
their own domains are not in the database yet, but will be added.
Okay, So a IADB whitelist test for...
anntaylor.outbound.ed10.com
...would work along the lines:
| anntaylor.outbound.ed10.com.iddb.isipp.com = 64.14.86.219 | 219.86.14.64.iadb2.isipp.com = 127.0.0.40
Where 40 means 10 "listed" + 3 * 10 "other reasons" resp. 10 "listed" + 20 "important reason" + 10 "other reason".
It's probably better to use the detailed codes offered by iadb.isipp.com, but I check this stuff with GetHostByAddr(), and then the single iadb2 code is good enough.
Yes:
anntaylor.outbound.ed10.com.iddb.isipp.com. 1H IN A 64.14.86.219
219.86.14.64.iadb.isipp.com. 1H IN A 127.0.100.7 219.86.14.64.iadb.isipp.com. 1H IN A 127.0.0.1 219.86.14.64.iadb.isipp.com. 1H IN A 127.0.0.2 219.86.14.64.iadb.isipp.com. 1H IN A 127.0.2.2
Still a bit too sender-centric for my likes, but perhaps workable.
In theory you could use this method to catch some dubious submissions. It's not exactly a whitelist, a spammer is free to buy an IADB entry ($ 500 + a monthly fee) as long as he follows the IADB definition of "legit". I'm certain that it's neither your nor my definition... <gd&r>
We could use it as a flag to check new records for FPs as opposed to am outright whitelist.
Jeff C.