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. The MX record for a domain that's enrolled in Exchange Online uses the syntax. Check with your domain registrar or DNS hosting service to verify the MX record for your domain is correct. If external senders receive this NDR when they send email to recipients in your domain, try the following fixes:įix your MX record: For example, it might be pointing to an invalid mail server. The most common issues and fixes are described in the following sections. Even your email admins can't do anything about service outages except wait for the problem to be resolved. Service outage: A problem with the whole Microsoft 365 or Office 365 service could be causing the problem. If you'd like more details about DNS records, see DNS basics. 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). Just wait: It might seem strange, but this error might go away on its own after a few days. 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. Here are some steps that you can try to fix the problem yourself. The email server that's generating the error doesn't accept email from the sender's domain (for example, This error is generally caused by email server or DNS misconfiguration. 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). It's frustrating when you get an error after sending an email message.
0 Comments
Leave a Reply. |