> look at previous emails; there's a bunch of similar issues

Easier, why don't consider positive answer only 127.0.0.>=2  so you can be
sure that whatever the problem with dns can be, a mail gets blocked ONLY if
the answer is within a given range. 

Besides that, I suppose the problem can be different than just a timeout.
Temporary failures, I have seen very fast wrong answers, like a firewall
doing some 'anti-ddos' filtering or something like that. It happened just a
few times in the last few years, and maybe it's because of a problem of
net-dns or the local windows resolver. 

And an easy startup test can be done just looking for a A RR for 127.0.0.2
that should be present in all dnsbl.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to