On Sun 03/03/2024 at 18:55, Andy Smith via mailop <[email protected]> wrote:
> Hi,
>
> On Sun, Mar 03, 2024 at 05:23:22PM +0000, Gareth Evans via mailop wrote:
>> (Error NOERROR looking up 23.24.6.165 PTR,Error Error NXDOMAIN looking
>> up 23-24-6-165-static.hfc.comcastbusiness.net. A looking up
>> 23-24-6-165-static.hfc.comcastbusiness.net. A,Error Error NXDOMAIN looking
>> up 23-24-6-165-static.hfc.comcastbusiness.net. AAAA looking up
>> 23-24-6-165-static.hfc.comcastbusiness.net. AAAA);
> Like it says, 23-24-6-165-static.hfc.comcastbusiness.net is an
> NXDOMAIn for both A and AAAA, so that's not going to get very far.
Thanks, I understand that.
Given:
Received: from atlas.bondproducts.com (unknown [23.24.6.165])
by mx6.messagingengine.com (Postfix) with ESMTP id ...
[...]
Received: from users.shellworld.net (users.shellworld.net [50.116.47.71])
by atlas.bondproducts.com (Postfix) with ESMTP id ...
atlas is (I think) a relay in this context.
$ dig -x 23.24.6.165
;; ANSWER SECTION:
165.6.24.23.in-addr.arpa. 3600 IN PTR
23-24-6-165-static.hfc.comcastbusiness.net.
What I am really asking is, if
23-24-6-165-static.hfc.comcastbusiness.net
actually resolved to 23.24.6.165 (same IP as atlas...), would delivery be
expected to succeed, or does the host in the PTR also have to be
atlas.bondproducts.com?
I think the latter is what Marco meant by "proper PTR", and there may indeed be
no convention.
The servers involved are not mine. I bumped into this issue after discovering
an invalid SPF record at shellworld.net. I've never dealt with relays, or PTR
records that don't correspond directly to sending hosts, so wondered what
should happen in those circumstances if the IP actually resolved.
Thanks both.
Gareth
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
