Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 550 5.4.1 Recipient address rejected: Access denied | SMTP log | -> EOP |
| Affected build range | Microsoft 365 | Product documentation | |
| Registry key involved | | | |
| Relevant service/endpoint URL | https://outlook.office.com/ecp | Exchange Admin Center | -> EOP |
| Log line signature | Event ID 6006 (delivery failure) and Event ID 6009 (message queued for retry) | MSExchangeTransport log | |
Log Files to Check
C:\Program Files\Microsoft\Exchange Server\V15\Logging\Transport\SMTP\Detailed.logC:\Program Files\Microsoft\Exchange Server\V15\Logging\Transport\QueueEngine\Detailed.log
What This Error Actually Means
The error code "550 5.4.1 Recipient address rejected: Access denied" is raised by Exchange Online Protection (EOP) when an email message is being processed and the recipient's mailbox does not exist, or there are restrictions in place that prevent delivery to the specified recipient address. This rejection can be due to various reasons such as incorrect configuration of transport rules, hybrid mail flow misconfiguration, or the sender domain being blocked by EOP policies.
Affected Versions and Scope
This error is prevalent across all builds of Microsoft 365 that include Exchange Online services. It applies to both on-premises environments integrated with Exchange Online (hybrid configurations) as well as purely cloud-based deployments. The error does not affect versions or tenants where EOP policies are disabled, such as certain compliance scenarios or when using third-party email filtering solutions.
Where To Look First: Logs and Event IDs
To diagnose this issue, start by examining the SMTP logs located at
C:\Program Files\Microsoft\Exchange Server\V15\Logging\Transport\SMTP\Detailed.log. You should look for entries that contain the exact error string "550 5.4.1 Recipient address rejected: Access denied". Additionally, check the QueueEngine log file located at
C:\Program Files\Microsoft\Exchange Server\V15\Logging\Transport\QueueEngine\Detailed.log to see if there are any related delivery failures or message queuing events.
Event IDs 6006 and 6009 in the MSExchangeTransport source provide additional context. Event ID 6006 signifies a delivery failure, while Event ID 6009 indicates that a message has been queued for retry due to temporary issues such as network connectivity problems or recipient address validation failures.
Root Causes
Recipient Mailbox Does Not Exist in Tenant
This is one of the most common reasons for this error. If the recipient's mailbox does not exist within your Exchange Online tenant, EOP will reject the message with a 550 5.4.1 error.
Sending Domain on Block List or Transport Rule Misconfiguration
If the sending domain is listed in an IP block list within EOP policies, or if there are transport rules that inadvertently reject messages from certain domains or users, this can cause the recipient address to be rejected with a 550 5.4.1 error.
Hybrid Mail Flow Misconfiguration
In hybrid environments where on-premises Exchange servers and Exchange Online coexist, misconfigurations in accepted domain routing settings can lead to messages being incorrectly routed or rejected by EOP if it is not authorized to accept mail for the on-premises domain.
Fix Procedure
- Verify Recipient Mailbox Existence: Use Exchange Online PowerShell to check if the recipient mailbox exists. Run
Get-Mailbox -Identity <recipient>. If no results are returned, proceed with creating a new mailbox.
- Create Missing Mailbox (if applicable): Execute
New-Mailbox -Name '<name>' -MicrosoftOnlineServicesID <upn> to create the missing recipient mailbox. Ensure that an Exchange Online Plan license is assigned in the Microsoft 365 admin center.
- Review and Adjust Transport Rules: List all enabled transport rules with
Get-TransportRule | Where-Object {$_.State -eq "Enabled"} | Select-Object Name,Priority,StopRuleProcessing,RejectMessageReasonText. Disable any problematic rules using Disable-TransportRule -Identity '<rule name>', test the change, and re-enable with corrected conditions.
- Check Hybrid Configuration: For hybrid environments, ensure that mail flow is correctly configured. Run
Test-MigrationServerAvailability to verify connectivity and use Get-AcceptedDomain | Select-Object DomainName,DomainType to confirm the recipient's domain type.
- Connector Configuration: In the Exchange Admin Center > Mail flow > Connectors, review the on-premises connector configuration to ensure it routes mail to the correct Exchange server MX or smart host. Ensure that the accepted domains are properly configured with
Get-AcceptedDomain | Select-Object DomainName,DomainType.
Disabling transport rules can affect message delivery for all users governed by those rules. Test changes in a controlled environment before applying them broadly.
Error Code Variants
| Code | Description |
| 550 5.1.3 | Recipient address rejected: Recipient is not allowed to receive mail from this sender. |
| 550 5.4.2 | Recipient address rejected: Recipient's mailbox is full or disabled. |
| 550 5.1.1 | Recipient address rejected: Recipient unknown (recipient does not exist). |
Verification
To verify that the issue has been resolved, monitor the MSExchangeTransport logs for Event ID 6009 messages indicating successful delivery retries or Event ID 6006 messages showing no further delivery failures. Additionally, check the Exchange Admin Center > Mail flow > Message trace to confirm that the recipient address is now accepted and the message was delivered successfully.
Prevention
To prevent recurrence of this issue, ensure regular audits of transport rules and hybrid mail flow configurations. Implement a policy for reviewing and updating these settings periodically to align with organizational changes or updates in EOP policies. Regularly check the IP Block List in EOP under Exchange Admin Center > Protection > Anti-spam to remove any outdated entries that may be causing false rejections.
By following these steps, you can effectively diagnose and resolve issues related to the "550 5.4.1 Recipient address rejected: Access denied" error in your Microsoft 365 environment, ensuring smooth email delivery for all users.