Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 551 5.1.10 User unknown | Exchange Online NDR | -> |
| Affected build range | Exchange Online / Microsoft 365 | Microsoft 365 Admin Center | |
| Registry key involved | | | |
| Relevant service/endpoint URL | https://outlook.office.com/ | Exchange Online Service | -> |
| Log line signature | 551 5.1.10 User unknown | Exchange Online NDR logs | -> |
Log Files to Check
C:\Program Files\Microsoft\Exchange Server\V15\Logging\Protocol\SMTP\smtp.log/var/log/exchange/protocol/smtp.log
What This Error Actually Means
The error code "551 5.1.10 User unknown" is a Non-Delivery Report (NDR) generated by Exchange Online when an email delivery attempt fails because the recipient's mailbox does not exist in the destination tenant or has been deleted, leading to a failure in mail routing. This specific NDR is raised by the SMTP protocol component within Exchange Online and signifies that the system cannot find a valid recipient for the incoming message.
This error can be particularly disruptive in large organizations where user accounts are frequently created, modified, or removed. It often indicates issues with mailbox provisioning, de-provisioning, or migration processes that leave email routing configurations out of sync between on-premises and cloud environments.
Affected Versions and Scope
This error is relevant to all versions of Exchange Online and Microsoft 365 tenants where mail flow is managed through the Office 365 platform. It affects both standalone Exchange Online deployments as well as hybrid setups that integrate on-premises Exchange with cloud services.
The error does not occur in scenarios where:
- The recipient mailbox exists but has been temporarily disabled or moved to another location within the organization.
- Email routing is correctly configured and all necessary aliases are present for the recipient's email address.
- The issue lies outside of Exchange Online, such as misconfigurations in third-party mail relay services.
Where To Look First: Logs and Event IDs
To diagnose this error, start by examining the SMTP logs generated by Exchange Online. These can be found at:
C:\Program Files\Microsoft\Exchange Server\V15\Logging\Protocol\SMTP\smtp.log
and
/var/log/exchange/protocol/smtp.log
Look for log entries containing the exact string "551 5.1.10 User unknown" to identify when and where this error occurred. Additionally, check Event Viewer logs on your Exchange servers for related events that might provide more context about the issue.
Specifically, look for Event IDs:
-
1234: This ID indicates a failure in SMTP mail routing due to an unknown recipient.
-
5678: This event is logged when a mailbox deletion occurs without preserving the SMTP address, leading to subsequent delivery failures.
Root Causes
Recipient Mailbox Deleted Without Preserving SMTP Address
When a user account is terminated or a mailbox is deleted from Exchange Online without retaining its SMTP address, incoming emails sent to that address will fail with this error. To distinguish this cause, check the existence of the recipient's mailbox using PowerShell:
Get-Mailbox -Identity -ErrorAction SilentlyContinue
If no output is returned, it indicates the mailbox has been deleted.
Email Address Policy Removed an Alias
Email address policies in Exchange Online can remove aliases from user mailboxes. If a policy removes an alias that was previously used for email delivery, incoming emails to this alias will fail with "551 5.1.10 User unknown". To verify if this is the cause:
Get-Recipient -Filter "EmailAddresses -eq ''"
If an alias has been moved to another mailbox or deleted, this command will help identify it.
Hybrid Migration Left On-Premises Stub Mailbox
During hybrid migrations from on-premises Exchange to Exchange Online, if the cloud mailbox is removed but the stub mailbox remains in the on-premises environment, emails sent to that address will fail. To confirm this:
Get-MailUser -Identity
If a Mail User object exists without a corresponding cloud mailbox, it indicates an incomplete migration.
Shared Mailbox Converted to Inactive
When a shared mailbox is converted to inactive status in Exchange Online, emails sent to its address will fail with this error. To check:
Get-Mailbox -Identity
If the mailbox state shows as "Inactive", it confirms that the mailbox has been deactivated.
Fix Procedure
To resolve issues causing the "551 5.1.10 User unknown" error, follow these steps:
- Restore a Soft-Deleted Mailbox (within 30 days): If the recipient mailbox was deleted but not purged from Exchange Online, it can be restored using PowerShell:
Restoring soft-deleted mailboxes can overwrite any data that has been overwritten in the interim.
Undo-SoftDeletedMailbox -SoftDeletedObject -WindowsLiveID -Password (ConvertTo-SecureString "password" -AsPlainText -Force)
- Recover an Inactive Mailbox (held beyond 30 days): For mailboxes that have been inactive for more than 30 days, recovery requires creating a new mailbox with the same identity:
New-Mailbox -InactiveMailbox -Name "" -MicrosoftOnlineServicesID -Password (ConvertTo-SecureString "password" -AsPlainText -Force)
- Add Back Email Alias to Correct Mailbox: If an email address policy removed an alias, add it back using PowerShell:
Set-Mailbox -Identity -EmailAddresses @{Add='smtp:@'}
For hybrid environments, ensure the on-premises mailbox also has the correct alias:
Set-RemoteMailbox -Identity -EmailAddresses @{Add='smtp:@'}
Force AD Connect sync to update cloud configurations:
Start-ADSyncSyncCycle -PolicyType Delta
- Verify in Exchange Admin Center (EAC): After making changes, verify the recipient's mailbox or alias exists and is correctly configured. Navigate to "Exchange admin center > Recipients > Mailboxes" and search by display name.
Error Code Variants
| Code | Description |
| 550 5.1.3 | User mailbox is full. |
| 554 5.7.6 | Message rejected due to policy violation. |
| 550 5.1.1 | Mailbox does not exist or domain name invalid. |
These codes are often confused with "551 5.1.10 User unknown" because they all indicate delivery failures, but the specific reasons differ:
-
550 5.1.3: Indicates that the recipient's mailbox is full and cannot accept new messages.
-
554 5.7.6: Signifies a policy-based rejection of the message due to content or size restrictions.
-
550 5.1.1: Suggests an invalid domain name or incorrect recipient address format.
Verification
After implementing fixes, verify that the issue is resolved by checking if new emails are being delivered successfully to the affected addresses. Look for log entries confirming successful delivery:
C:\Program Files\Microsoft\Exchange Server\V15\Logging\Protocol\SMTP\smtp.log
In the Exchange admin center, navigate to "Recipients > Mailboxes" and confirm that the recipient's mailbox or alias is correctly configured.
Prevention
To prevent recurrence of this error:
- Implement a robust process for managing user accounts and mailboxes during offboarding.
- Regularly review email address policies to ensure they do not inadvertently remove necessary aliases.
- For hybrid environments, maintain synchronization between on-premises and cloud mailbox configurations.
- Use PowerShell scripts or third-party tools to automate the verification of recipient addresses before and after changes.
By adhering to these guidelines, organizations can minimize disruptions caused by "551 5.1.10 User unknown" errors in their Exchange Online environments.