> -----Original Message----- > From: John Rudd [mailto:[EMAIL PROTECTED] > Sent: vrijdag 20 oktober 2006 0:18 > To: Mark > Cc: users@spamassassin.apache.org > Subject: Re: R: Scoring PTR's > > > > I now see the cause of your confusion. "Make sure your PTR > > and A records match", in this context, means, exactly as the RFC > > states, that "For every IP address, there should be a matching PTR > > record in the in-addr.arpa domain." And "That all IP addresses > > have a corresponding PTR record." > > AND that the PTR record point back to a valid A record. > > Further into the same paragraph it says: > > Also, PTR records must point back to a valid A record, > > Given that the point of this paragraph is "Make sure your PTR and A > records match", I would comfortably assert that one necessary > element to making this A record "valid" is that at least one such > A record from that hostname matches the IP address for that PTR record.
That does NOT mean that other A records cannot resolve to, and thus be used for, the same IP address. That's the whole point: not if someone has defined a valid A record for a PTR; but whether the PTR of the reverse DNS lookup should match that of the A record used. Received: from mail.apache.org (hermes.apache.org [209.237.227.199]) Even if hermes.apache.org actually used "hermes.apache.org" for HELO, then still, there's nothing in any RFC, that says that their PTR should also be "hermes.apache.org" (RFC 1912 just says that for whatever PTR they use, a matching A record should exist also). That's what we're talking about here. Not whether an A record exists to match the PTR, but whether the A record used for HELO should match the PTR. And I remaim firm in my conviction that this is not the case. - Mark
