Having a client doing a test from the MSFT exchange tools site, which is failing.
NOQUEUE: reject: RCPT from unknown[13.67.59.89]: 450 4.7.1 Client host rejected: cannot find your reverse hostname, [13.67.59.89];
NetRange: 13.64.0.0 - 13.107.255.255
CIDR: 13.96.0.0/13, 13.104.0.0/14, 13.64.0.0/11
NetName: MSFT
A bit of an oversight?
/kc
Which "Exchange tools site" are you referring to?
Happy to help get this fixed up.
-jeff
Ken,
A little difficult to say what this without knowing what 13.67.59.89 actually is. If this is an Azure deployment, ReverseFqdn needs to be populated on the Public IP address resource. Please take a look here https://docs.microsoft.com/en-us/azure/dns/dns-reverse-dns-for-azure-services
Thanks,
Christian
Im not exactly sure what this is either, the client sent me a screenshot
that called itself the "microsoft connectivity analyzer", which had several
steps testing deliverability of email to their domain, with the final test
of an actual test email delivery failing.
/kc
Nope.
NetRange: 13.64.0.0 - 13.107.255.255
CIDR: 13.64.0.0/11, 13.96.0.0/13, 13.104.0.0/14
NetName: MSFT
NetHandle: NET-13-64-0-0-1
Parent: NET13 (NET-13-0-0-0-0)
NetType: Direct Assignment
OriginAS:
Organization: Microsoft Corporation (MSFT)
RegDate: 2015-03-26
Updated: 2015-03-26
OrgName: Microsoft Corporation
OrgId: MSFT
Address: One Microsoft Way
City: Redmond
StateProv: WA
PostalCode: 98052
Country: US
RegDate: 1998-07-09
Updated: 2017-01-28
Comment: For routing, peering or DNS issues, please
Comment: contact:
Comment: * IOC@microsoft.com
It's one of the outbound IP addresses for the Microsoft Remote Connectivity
Analyzer, as documented here:
https://support.office.com/en-gb/article/office-365-urls-and-ip-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2
.
Your client's mail exchanger is rejecting the test e-mail message because
that particular outbound IP address does not have PTR resource record.
Interestingly, all of the IP addresses listed do not.
Josh
13.67.59.89/32 should reverse to |
testconnectivity.microsoft.com
*Optional:* Remote Connectivity Analyzer
<https://testconnectivity.microsoft.com/> - Initiate connectivity tests.
>
testconnectivity.microsoft.com
no
>
13.67.59.89/32
40.69.150.142/32
40.85.91.8/32
104.211.54.99/32
104.211.54.134/32
TCP 80 & 443
-Hank
Hah. Thanks. 
Yes, it's a big shop..
I've escalated this to the team responsible for the tool. Will report back when we have some resolution.
Thanks for calling out the issue.