On Fri, Nov 26, 2004 at 02:35:51PM -0700,
administrator(_at_)yellowhead(_dot_)com wrote:
Once again I will point out the problems of verifying mail based on PTR
records, only this time I have a very good example.
Er, this is the SPF list, not the PTR list ?
X-Pobox-Antispam: Require PTR Record returned DENY: 139.142.165.243 has no
PTR record
X-Sift-Reason: require_ptr returned DENY: 139.142.165.243 has no PTR record
--------------------------------------------------------
Why did the reverse lookup suddenly stop working? There are basically two
servers with authority for the 142.139.in-addr.arpa domain
(ns2.toroon.groupetelecom.net & ns1.clgrab.groupetelecom.net). The first
one directs you to the root servers, and the second directs you to
ns1.vip.net & ns2.vip.net. So it all depends on which one your server asks
as to whether or not it gets the proper answer.
"BUT THE SERVER IS BROKEN!" you say. So what; just try to get it fixed.
You cannot get this fixed, therefore your email is rejected by pobox,
thus you use it as an example on the SPF list ?
Also, you seem to know it is your DNS that is hosed. If you cannot
get this fixed by contacting dnsadmin(_at_)cg(_dot_)sfl(_dot_)net then you may
experience
other (DNS related) problems as well.
If your provider has another problem, one where it uses port 26 for
outbound mail, is _that_ something we also should not check on?
Yes, this is an extreme example.
Alex
--
I ask you to respect any "Reply-To" and "Mail-Follow-Up" headers. If
you reply to me off-list, you'd better tell me you're doing so. If
you don't, and if I reply to the list, that's your problem, not mine.