Sending, receiving, and organizing email in Outlook on the web for business
For this scenario, the most effective first step is to run a Message Trace in Exchange Admin Center to determine whether the messages ever reached the Microsoft 365 tenant and what happened to them.
Recommended investigation path:
- In the Exchange Admin Center, run a Message Trace for the affected sender and recipient mailboxes.
- Review the result status:
- Failed: the message was rejected. Check the error details for the rejection reason.
- Quarantined: the message was stopped by filtering and held in quarantine.
- Delivered: the message reached the mailbox, so the issue may be mailbox rules, client view, or message placement.
- Ask the sender for any non-delivery report (NDR) or bounce message they received. The NDR often contains the exact SMTP error code and reason.
- If the messages never reached the tenant, the sender should review their sending system and NDR details.
- If the NDR shows the sender IP was blocked with an error like 550 5.7.606-649 Access denied, banned sending IP, the sender should use the Anti-Spam IP Delist Portal at https://sender.office.com/.
- If the sender is getting a temporary restriction such as 451 4.7.550 Access denied, please try again later, that indicates Microsoft 365 temporarily throttled traffic from the source IP while it is being evaluated.
- If the messages are landing in Junk Email instead of Inbox, the recipient can submit the false positive message to Microsoft for analysis.
Additional checks:
- Since the blocked senders list was already checked, also verify whether the message was quarantined or filtered before mailbox delivery.
- If only specific messages are missing while other mail from the same sender is delivered, that can indicate a message-specific filtering or rejection issue rather than a general mail flow problem.
- If the sender is connecting with an incorrectly advertised private or nonroutable IP, Microsoft 365 or Outlook.com might not accept the mail. Reserved private ranges include:
-
192.168.0.0/16 -
10.0.0.0/8 -
172.16.0.0/11
-
If external sender-side remediation is needed, the sender should follow the instructions in the NDR first, then use the delist portal if the error specifically indicates a banned sending IP.
References:
- Find and fix email delivery issues as a Microsoft 365 for business admin
- External senders - Troubleshoot email sent to Microsoft 365
- External senders - Use the delist portal to remove yourself from the blocked senders list and address 5.7.511 Access denied errors
- Microsoft 365 services for external email senders