- 4 minutes to read
It's frustrating when you get an error after sending an email message. This topic describes what you can do if you see error code 5.4.1 in a non-delivery report (also known as an NDR, bounce message, delivery status notification, or DSN).
Why did I get this bounce message?
The email server that's generating the error doesn't accept email from the sender's domain (for example, @fabrikam.com). This error is generally caused by email server or DNS misconfiguration.
|I got this bounce message. How do I fix it?||I'm an email admin. How can I fix this?|
I got this bounce message. How do I fix it?
Here are some steps that you can try to fix the problem yourself.
If the steps in this section don't fix the problem for you, contact your email admin and refer them to the information in this topic so they can try to resolve the issue for you.
Just wait: It might seem strange, but this error might go away on its own after a few days. If your email admin made changes to your organization's domain name system (DNS) records, the change can prevent you from sending and receiving email for a brief period, even if they did everything correctly (it can take up to 72 hours for DNS changes to propagate on the internet). If you'd like more details about DNS records, see DNS basics.
Service outage: A problem with the whole Microsoft 365 or Office 365 service could be causing the problem. Even your email admins can't do anything about service outages except wait for the problem to be resolved.(Video) Email Undeliverable | Error code 5.1.10 in Office 365 | Update accepted domain settings | Exchange
I'm an email admin. How can I fix this?
The most common issues and fixes are described in the following sections.
Incorrect MX record
If external senders receive this NDR when they send email to recipients in your domain, try the following fixes:
Fix your MX record: For example, it might be pointing to an invalid mail server. Check with your domain registrar or DNS hosting service to verify the MX record for your domain is correct. The MX record for a domain that's enrolled in Exchange Online uses the syntax <domain>.mail.protection.outlook.com.
Verify only one MX record is configured for your domain: We don't support using more than one MX record for domains enrolled in Exchange Online.
Test your MX record: Use the Outbound SMTP EMail test in the Microsoft Remote Connectivity Analyzer.
Domain configuration issues
Open the Microsoft 365 admin center.
Click Domains and verify your domain appears in the list as Active.
Select the domain and click Troubleshoot. Follow the troubleshooting wizard steps.(Video) SOLVED 550 5.7.520 Access Denied Organization Does Not Allow External Forwarding
If you control of the DNS records for your Microsoft 365 or Office 365 domain, you can also check the status of the domain in the Exchange admin center (EAC) by following these steps:
In the Microsoft 365 admin center, click Admin > Exchange.
Click Mail flow > Accepted domains.
Verify that your domain is listed, and verify the Domain Type value for the domain. Typically, the value should be Authoritative. However, if you have properly configured a shared domain, the value might be Internal Relay.
Updated DNS records haven't propagated
You updated your domain's DNS records correctly for Microsoft 365 or Office 365, but the changes haven't propagated to all DNS servers on the internet. Changes to your domain's DNS records might take up to 72 hours to propagate to all DNS servers on the internet.
Hybrid deployment configuration issues
If your domain is part of a hybrid deployment between on-premises Exchange and Exchange Online, check the following items:
- Verify the configuration of the Send connectors and Receive connectors in your on-premises Exchange organization that are used for hybrid. These connectors are configured automatically by the Hybrid Configuration Wizard, and the wizard might need to be run again by your Exchange administrator.
For more information, see this topic.
For more information about transport routing in hybrid deployments, see Transport Routing in Exchange Hybrid Deployments.
Service issues in Exchange Online
A service issue in Microsoft 365 or Office 365 might be causing the problem. To check the status of Microsoft 365 or Office 365, do the following steps:
Open the Microsoft 365 admin center.
Click Service health to see an overview of any issues.
Select View all to a get more details about all known issues.
Details about this NDR
The Exchange Online non-delivery report (NDR) notification for this specific error might contain some or all of the following information:
User information section
Relay Access Denied
The outbound connection attempt was not answered because either the remote system was busy or it was unable to take delivery of the message.(Video) How to fix your message wasn t delivered because the recipient's email provider rejected it(new)
Diagnostic information for administrators section
No answer from host.
#550 5.4.1 Relay Access Denied ##
Still need help?
Email non-delivery reports in Exchange Online
Use Directory-Based Edge Blocking to reject messages sent to invalid recipients in Exchange Online