niclas wrote: > > smtp2-1.tng.de has address 213.178.66.95 > 95.66.178.213.in-addr.arpa domain name pointer smtp2-1.tng.de. > smtp2.tng.de has address 213.178.64.96 > smtp2.tng.de has address 213.178.64.95 > Host 96.64.178.213.in-addr.arpa not found: 3(NXDOMAIN) > Host 95.64.178.213.in-addr.arpa not found: 3(NXDOMAIN) > > so they DO exist, it's just that DNS ans HELO name don't match.
That "2-1" may look like some poor sort of classless delegation... I think they messed up their zone files. >> The one causing your error is a >> spam-protection feature. > > i don't see how this should prevent spammers from doing anything. spam > protection is a complicated thing and cannot be done by simple checkups. Used to. Admins of reliable systems used to be savvier than spammers. That's how opt BOFHCHECKHELO came. Later, SPF introduced a similar check. See http://www.courier-mta.org/courier.html > > oh, and they said, their smtp-systems are a cluster, so DNS-lookup > *cannot* work all the time anyway. still sounds like they're right. They are not. They have DNS delegation for the whole class, so they can implement whatever view they like, the way they like. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
