You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When users try to send mail from Microsoft 365 to an external recipient, the destination message transfer agent (MTA) rejects the message. The error message that users receive may vary. Typically, it states that the source server's host name does not match its IP address.
26
+
When users try to send mail from Microsoft 365 to an external recipient, the destination message transfer agent (MTA) rejects the message. The error message that users receive may vary. Typically, it states that the source server's host name doesn't match its IP address.
27
27
28
28
## Cause
29
29
30
-
The recipient server requires that the server name that's contained in the message HELO string have a corresponding pointer (PTR) resource record (reverse IP lookup). Microsoft 365 use multiple IP addresses to send mail. Because of DNS limitations, all these IP addresses can't be mapped through the PTR record to the server name that's in the message HELO string.
30
+
The recipient server requires that the server name that's contained in the message HELO string have a corresponding pointer (PTR) resource record (reverse IP lookup). Microsoft 365 uses multiple IP addresses to send mail. Because of DNS limitations, all these IP addresses can't be mapped through the PTR record to the server name that's in the message HELO string.
31
31
32
32
## Resolution
33
33
34
-
The method in which Microsoft 365 send email by using multiple IP addresses is typical for most large mail systems and is by design. Contact the recipient system administrator for help.
34
+
The method that Microsoft 365 uses to send email messages by using multiple IP addresses is standard for most large mail systems and is by design. Contact the recipient's system administrator for help.
35
35
36
36
## More information
37
37
38
-
In Microsoft 365, outgoing email settings use specific patterns. It's important to be aware of these patterns if your recipient servers use PTR record lookups for validation. This is because they explain why messages that are sent from the service might be rejected. The patterns are as follows:
38
+
In Microsoft 365, outgoing email settings use specific patterns. It's important to be aware of these patterns if your recipient servers use PTR record lookups for validation. This is because they explain why messages sent from the service might be rejected. The patterns are as follows:
39
39
40
-
1. The sending IP addresses that are used by Microsoft 365 have forward-confirmed reverse DNS records. This means that each sending IP address has both a forward (name-to-IP address) and a reverse (address-to-name) DNS record that contains matching information. For example:
40
+
1. The sending IP addresses used by Microsoft 365 have forward-confirmed reverse DNS records. This means that each sending IP address has both a forward (name-to-IP address) and a reverse (address-to-name) DNS record that contains matching information. For example:
2. The HELO/EHLO strings that are used to identify the mail servers that are used by the service also contain `outbound.protection.outlook.com`. For example:
48
+
2. The HELO/EHLO strings which identify the mail servers that the Microsoft 365 service uses also contain `outbound.protection.outlook.com`. For example:
49
49
`na01-bn1-obe.outbound.protection.outlook.com`
50
50
51
-
All these HELO/EHLO strings have A records that contain some outgoing IP addresses that correspond to the sending mail servers. (However, the A records do not contain all these outgoing IP addresses.) For example:
51
+
All these HELO/EHLO strings have A records that contain some outgoing IP addresses that correspond to the sending mail servers. However, the A records don't contain all these outgoing IP addresses. For example:
A record: `na01-bn1-obe.outbound.protection.outlook.com`:
@@ -64,9 +64,9 @@ In Microsoft 365, outgoing email settings use specific patterns. It's important
64
64
207.46.163.158
65
65
207.46.163.149
66
66
67
-
3. The PTR records of the IP addresses in the A record of the EHLO/HELO string will not match the HELO/EHLO string of the sending mail server. For example:
67
+
3. The PTR records of the IP addresses in the A record of the EHLO/HELO string won't match the HELO/EHLO string of the sending mail server. For example:
0 commit comments