Fix Microsoft 365 Incoming Email Bounces with 550 5.7.1 Relaying Denied Error
Question details
Users are experiencing incoming email bounces with a 550 5.7.1 relaying denied error after renewing a domain or resetting DNS configurations.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Receiving incoming emails after a domain renewal or modifying DNS configurations at the domain registrar.
- Observed behavior
- Outbound emails work successfully, but incoming messages bounce back to external senders with a 550 5.7.1 relaying denied error code.
Ensure you have administrator access to your domain registrar's DNS management portal and the Microsoft 365 Admin Center to review mail flow settings.
Disable Domain Registrar Spam Filtering
Resolve routing conflicts caused by third-party spam or malware filtering at the domain registrar blocking inbound Microsoft 365 mail.
Many domain registrars provide built-in email routing or spam filtering services. If these features are accidentally enabled during a DNS reset or domain renewal, they intercept incoming emails before they reach Microsoft 365, causing relay errors.
Access the account where you purchased or manage your custom domain (e.g., GoDaddy, Namecheap, Network Solutions).
Navigate to the email routing, forwarding, or spam filtering settings associated with your domain.
Temporarily disable the registrar's built-in spam and malware filtering services, ensuring email routing is set to remote or external exchange.
Send a test message from a personal external email account (like Gmail or Yahoo) to your Microsoft 365 address to verify if the bounce error persists.

Verify MX Records and Run Connectivity Analyzer
Ensure your domain's MX records point correctly to Microsoft 365 and use Microsoft's official diagnostic tool to test inbound SMTP flow.
Isolate the Issue Using the Default Domain
Determine if the issue is strictly tied to your custom domain's DNS routing by testing with the default Microsoft tenant domain.
Need a Reliable and Free Office Suite Alternative?
While troubleshooting Microsoft 365 Exchange email routing issues, you might be looking for a lightweight, cost-effective alternative for your document management. WPS Office provides a free, fully compatible suite for creating and editing Word, Excel, and PowerPoint files without the overhead of complex cloud administration.
- 1. Visit the WPS Office Website: Go to the official WPS Office site to access the free download page.
- 2. Download the Installer: Select the appropriate version for your operating system and download the lightweight installation package.
- 3. Install and Edit: Run the installer, open WPS Office, and seamlessly start working on your existing Microsoft Office documents.

Frequently Asked Questions
What does '550 5.7.1 Relaying Denied' mean in Microsoft 365?
This error indicates that the email server receiving the message doesn't recognize the recipient domain as its own and refuses to forward (or relay) the message. It commonly happens if DNS records are misconfigured or external registrar filters intercept the mail after a domain renewal.
Why can I send outbound emails but not receive inbound ones?
Outbound emails originate from authenticated Microsoft 365 servers and don't rely on your domain's MX records to leave the network. Inbound emails, however, strictly rely on correct DNS routing (MX records) and external spam filters to find their way to your Microsoft 365 inbox.
How long does it take for MX record changes to resolve the bouncing issue?
DNS changes, including MX record updates and disabling registrar filters, can take anywhere from a few minutes to 48 hours to fully propagate across the internet, depending on your domain registrar's Time to Live (TTL) settings.
Can third-party domain registrars block my Microsoft 365 emails?
Yes. Many domain registrars include default email routing or spam filtering services. If these features are active, they might intercept inbound mail meant for Microsoft 365, failing to deliver the message and generating 550 relay errors.




