On Sun, 28 Jan 2007, Devin Ganger wrote:
On 1/28/07 8:35 PM, <stuart(_at_)bmsi(_dot_)com> wrote:
On Sun, 28 Jan 2007, Don Lee wrote:
There is a large and growing number of mailservers "out there" that
try to resolve the HELO name, and some do rDNS on the IP and
ensure that it matches the HELO.
All PTR records provide is a name - that you have to verify by checking
that it resolves to the IP. Well, guess what, a HELO name is a ... name
that you can verify by checking that it resolves to the IP - clearly
establishing that the domain owner designated that IP. So why
did you bother fetching the PTR records again?
Because by checking that A and PTR agree, I am confirming that the domain
that the machine claims to be is in fact authorized to be using that IP
address (barring institutional stupidity from ISPs who don't allow customers
to update rDNS information on a timely basis).
Yes, but checking that the name provided by HELO agrees *already* checks
that. Fetching PTR doesn't add anything.
Quick example to make sure you understand:
Connect from 188.8.131.52
Lookup A record:
mail.example.com IN A 184.108.40.206
That name and A record are the as you would get by first looking up:
220.127.116.11.in-addr.arpa IN PTR mail.example.com.
There is no need to lookup the PTR, because HELO has already provided it.
Bogus names can be provided in PTR just as easily as in HELO. Verifying
the A record validates either one.
Just think of HELO as a extra PTR that comes for free with an SMTP connection.
The difference is that the rDNS is normally less under the control of
the spammer. The HELO is arbitrary, and under the control of the MTA.
rDNS control requires more effort on the part of the spammer, and
will not be easy somewhere like x.y.rr.com or p.d.q.verizon.com.
rDNS can therefore be used to detect certain kinds of forgery that
resolving the HELO cannot.
For instance, It is easy for me to set up spamdomain.com -> 18.104.22.168, and
set up SPF so that 22.214.171.124 is OK to send mail. However, if
rr.com "owns" 126.96.36.199, they may not let me change the
rDNS to "spamdomain.com" - esp. if it's a "pool" IP.
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
please go to http://v2.listbox.com/member/?list_id=735