Shulou(Shulou.com)06/02 Report--

Collect some summary and analysis of the DSN code of non-delivery report from Microsoft manufacturer engineer and share it with you, which will be of great help to encounter email delivery problems.

DSN error code 4.4.7 in Exchange Online and Office 365

Problem analysis:

If you get the DSN error code 4.4.7 and the problem occurs only when sending an e-mail message to a recipient in a domain, the problem may be related to that target domain. The causes of domain problems may include:

A temporary network problem or Internet connection problem occurred in the target domain.

Strict anti-spam settings in the target domain block legitimate senders, for example, all senders in any domain in Exchange Online.

Solution:

Solution 1: the mail exchange (MX) record for the domain may be missing or incorrect. Learn more about how MX records work in the Domain name system (DNS) in DNS fundamentals.

Solution 2: you can test MX records and whether messages can be sent from your organization by using "verify MX records and outbound connector tests" under Office 365 > Mail flow configuration in Microsoft Remote Connectivity Analyzer.

Solution 3: the Sender Policy Framework (SPF) record for the domain may be incomplete and may not contain all mail sources for the domain. For more information about validating SPF records, see customizing SPF records to verify outbound e-mail messages sent from the domain.

Solution 4: the domain may expire due to non-payment. Confirm with your domain registry that your domain is active and has not expired.

Solution 5: mixed deployment configuration issues. If the domain is part of a mixed deployment between Exchange and Exchange Online, and the recipient is in the local organization, the problem may be related to the mixed configuration. Please provide the information in NDR to your local Exchange administrator. They may need to run the mixed configuration wizard again because of changes in local IP addresses or firewall rules.

2. DSN error code 5.1.0 in Exchange Online and Office 365

Problem analysis:

The mail server that generated the NDR 5.1.0 error does not accept messages from the sender or to the recipient. This can happen if the sender's e-mail address, IP address, or e-mail service provider is blocked.

Solution:

Fix incorrect SPF records

The Sender Policy Framework (SPF) record for your domain may be incomplete and may not contain all email sources for your domain. For more information about how to verify SPF records, see customizing SPF records to verify outbound emails sent from your domain.

Remove the sender from the recipient's block list

Your email address may be on the block list maintained by the recipient. If you can send messages to other recipients in the same domain, this may be the reason.

Ask the recipient to verify that your email address is not included in their block list. If it is included in the block list, delete it.

Delete the error entry in the autocomplete list

You may have selected items on the autocomplete list that are no longer working properly. This list is also known as the nickname cache. For example, the recipient may have moved from the local Exchange organization to Exchange Online, or vice versa. Although the recipient's e-mail address remains the same, other internal identities of the recipient may have changed, invalidating the entry you cached for the recipient.

DSN error codes 5.1.1 to 5.1.20 in Exchange Online and Office 365

Problem analysis:

A notification email (also known as a non-delivery report (NDR)) received in your email inbox may indicate that the address you specified cannot be found or that the address you specified is invalid, or that your Outlook or Outlook Web App recipient automatically completes an entry error in the cache. You receive this notification for the following common reasons:

The person or mailbox to which you are trying to send a message may not be found on the target email server.

You do not have permission to send messages to the distribution group or to one of the subgroups of the distribution group.

The user or mailbox to which you are trying to send email has an email setting called MX resource record, and this setting is not up to date.

The user or mailbox to which you are trying to send an email has set a rule to forward the message to another address, but the rule does not work properly.

Solution:

From the client point of view:

Solution 1: make sure the recipient's email address is correct

Solution 2: remove the recipient's email address from the autocomplete list

Solution 3: make sure the recipient does not have email forwarding rules set

Solution 4: make sure your email account is not compromised

Did you not send the original email at all? If not, your email address may be misused by spammers or others when sending emails.

Solution 5: make sure NDR is relevant to the email you actually send

From the administrator's point of view:

Solution 1: check the Office message center for configuration problems or service-scoped issues

Log in to the Office 365 portal using the administrator account through https://portal.office.com, and then do the following from the Dashboard:

1) check the "message Center" to see if your organization has known configuration problems.

a. Select message Center.

b. Select View all.

c. Select prevent or fix problems, and then perform any recommended actions.

2) check if there are any current service problems affecting the user's account in Office 365.

d. Select Service Health to view an overview of any issues.

e. Select View all for more details on all known issues.

3) check for incorrect or outdated MX resource records in the sender and recipient domain by running the mail flow troubleshooter tool in Office 365

Solution 2: update outdated Mail Exchange (MX) resource records

Error code 5.1.1 may be caused by a problem with message exchange (MX) resource records in the recipient's domain. For example, the MX record may point to the old mail server, or the recent configuration change may cause the MX record to be ambiguous.

Solution 3: if you reply to a re-created or migrated mailbox, update the user's autocomplete list

This NDR is usually caused by replying to an old message, or updating an old meeting request, and the recipient has the same email address, but something about the recipient's mailbox has changed. For example, a user's mailbox may have been deleted and recreated, or migrated from Exchange Online to the local Exchange. If the recipient email address format in NDR is IMCEAEX-_O=@, the reply may be an old email.

Solution 4: update forwarding rules to delete incorrect addresses

NDR is sometimes caused by the indirect recipient of the message. It may be because the target recipient has set up forwarding rules or proxies for their mailboxes. In addition, the recipient's e-mail administrator may have created a transport rule that copies or forwards messages to an invalid recipient e-mail address. For more information about these issues, see configuring email forwarding for mailboxes or quietly copying messages to auditors using transport rules.

4. DSN error code 5.4.1 in Exchange Online and Office 365

Problem analysis:

The mail server that generated this error does not accept messages from the recipient's domain. This error is usually caused by improper configuration of the mail server or DNS.

Solution:

Incorrect MX record

If an external sender receives this NDR when sending a message to a recipient in your domain, try the solution described in this section.

The message exchange (MX) records for your domain may be incorrect. For example, it may point to an invalid mail server. Please check with your domain registry or DNS managed service to verify that the MX of your domain is correct. The MX record for a domain that has been registered with Exchange Online uses the syntax .mail.protection.outlook.com.

And verify that only one MX record is configured for your domain. Using multiple MX records for domains registered in Exchange Online is not supported.

Updated DNS records have not yet been propagated

You correctly updated the DNS record for your domain for Office 365, but the changes have not yet been propagated to all DNS servers on Internet. Changes to the DNS records of your domain may take up to 72 hours to propagate to all DNS servers on Internet.

Mixed deployment configuration issu

If your domain is part of a mixed deployment between Exchange and Exchange Online, check the following items:

Verify the configuration of send and receive connectors for mixed deployment in your local Exchange organization. These connectors are automatically configured by the mixed configuration wizard, which your Exchange administrator may need to run again.

5. DSN error code 5.4.6 in Exchange Online and Office 365

Problem analysis:

There may be two reasons:

Depending on the domain in the recipient's e-mail address, your Exchange Online organization accepts the message, but may not be able to route the message correctly to the recipient. This may be caused by a problem with accepting domain settings.

In a mixed environment, some connectors in your Exchange Online organization are misconfigured.

Solution:

Accept domain problem

Verify that the recipient's domain is configured as an authoritative accepted domain in Exchange Online.

Mixed configuration problem

If your domain is part of a mixed deployment between Exchange and Exchange Online, check the following items based on your configuration:

You route all incoming messages from your mixed domain through Exchange Online.

This error may occur if the MX record for your mixed domain points to Exchange Online and the outbound connector used to route messages to your local Exchange organization is configured to use DNS routing.

To fix this problem, configure a dedicated outbound connector that uses smart host routing and configures your local hybrid server as a smart host. The easiest solution to this problem is to rerun the mixed configuration wizard in the local Exchange organization. You can also verify the configuration of the outbound connector for hybrid deployment by performing the following steps:

Open the Office 365 portal through https://portal.office.com, and then click Administration > Exchange. In Exchange Central Administration, click Mail flow > Connector. In the outbound Connectors section, select the connector for the mixed deployment, and then click Edit. On the delivery tab, verify that routing messages through Smart Host is selected and that the correct IP address or fully qualified domain name (FQDN) is specified for the smart host.

You route all outgoing messages from the Exchange Online server through your local hybrid server.

This configuration is controlled by the value of the RouteAllMessagesViaOnPremises parameter on the outbound connector for the hybrid server. If the value of this parameter is $true for the connector, you will route all outgoing messages from Exchange Online through your local hybrid server. You can verify this value by running the following command.

Get-OutboundConnector | Format-List Name,RouteAllMessagesViaOnPremises

In this configuration, the error is caused by one of the following:

You do not have an inbound connector with a Connector Type value of Local.

The inbound connector for the hybrid server is scoped to one or more accepted domains.

To fix this problem, configure a dedicated inbound connector whose Connector Type value is Local and whose scope is not in any accepted domain. The easiest solution to this problem is to rerun the mixed configuration wizard in the local Exchange organization. You can also verify the configuration of the inbound connector for mixed deployment by performing the following steps:

a. Open the Office 365 portal through https://portal.office.com, and then click Administration > Exchange.

b. In Exchange Central Administration, click Mail flow > Connector. In the inbound Connectors section, select the connector for the mixed deployment, and then click Edit. Verify the following information:

General verification to see if Local is selected.

Scope verifies whether the accepted domain is empty

6. DSN error codes 5.7.1 to 5.7.999 in Exchange Online and Office 365

Problem analysis:

This error usually indicates that an email security setting in your organization prevents your message from being delivered to the recipient. It may be one of the following questions:

You do not have permission to send a message to this recipient.

You do not have permission to send messages to this distribution group or one of its subgroups.

You do not have permission to send email through the email server between you and the recipient.

Your message was routed to the wrong email server.

Solution:

If the sender is outside your organization-configure the recipient or your mail server to accept messages from external or anonymous senders.

An external user attempts to send a message to a mail-enabled public folder in Office 365-if an external user attempts to send a message to a mail-enabled public folder in Office 365, they will receive a NDR with the following error code:

The remote server returned "# 5.7.1 smtp;550 5.7.1 RESOLVER.RST.AuthRequired; requires authentication [Stage: CreateMessage] >"

To change this behavior so that mail-enabled public folders can accept messages from external senders, perform the following steps:

Connect to the Exchange Online by using a remote PowerShell. For steps on how to do this, see connecting to Exchange Online using remote PowerShell. Add anonymous account permissions to the public folder. To do this, run the following command:

Add-PublicFolderClientPermission-identity-User Anonymous-Acce***ights CreateItems

See Knowledgebase article 2984402.

If the sender is outside your organization and his email server IP address is placed on the Microsoft Block list-in these cases, the NDR received by the sender will contain the information in the diagnostics section for the administrator, as follows: 5.7.1 service is not available; client host [xxx.xxx.xxx.xxx] is blocked using Block list 1 To request removal from the list, forward this message to delist@messaging.microsoft.combr/ > 5.7.1 the service is not available; block the client host [xxx.xxx.xxx.xxx] using Block list 1; to request removal from the list, forward this message to delist@messaging.microsoft.com

The domain is not fully registered in Office 365-if the domain is fully registered, try the following steps:

Verify that your domain is displayed as "Active" in the Office 365Portal (https://portal.office.com)).

For information about adding your domain to Office 365, see domains in Office 365.

To resolve domain validation issues, see Microsoft Knowledgebase article 2515404.

Incorrect MX record

Incorrect SPF records-Sender Policy Framework (SPF) records for your domain may be incomplete and may not contain all mail sources for your domain. For more information about validating SPF records, see customizing SPF records to verify outbound e-mail messages sent from your domain.

Hybrid on-premises and cloud deployment configuration issues-if your domain is part of a hybrid deployment between Exchange and Exchange Online, check the following items.

Even though the mixed configuration wizard automatically configures the inbound and outbound connectors in the Exchange Online Protection (EOP) service, you can still verify that these connector settings are correct. If the connector for the mixed deployment is not configured correctly, your Exchange administrator needs to rerun the mixed configuration wizard in the local Exchange organization.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.