Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 550 5.2.0 RESOLVER.ADR.InvalidInSmtpAddress | NDR email body | -> |
| Affected build range | Microsoft 365 / Exchange Online | Product documentation | |
| Registry key or OMA-URI involved | | | |
| Relevant service/endpoint URL | admin.microsoft.com > Exchange admin center > Mail flow > Message trace | Exchange Online portal | -> |
| Log line signature | 550 5.2.0 RESOLVER.ADR.InvalidInSmtpAddress | EOP logs | |
Log Files to Check
NDR email bodyadmin.microsoft.com > Exchange admin center > Mail flow > Message trace
What This Error Actually Means
The error code "550 5.2.0 RESOLVER.ADR.InvalidInSmtpAddress" is generated by Exchange Online when it encounters an invalid SMTP address during the delivery process of a message. The component responsible for raising this error is the Address Resolution Service (RESOLVER) within the Microsoft 365 platform, specifically in the context of resolving recipient addresses to their corresponding mailboxes or distribution groups. This error indicates that the destination mailbox address is either malformed, ambiguous, or refers to an object that no longer exists due to being disabled, soft-deleted, or having invalid SMTP proxy addresses.
Affected Versions and Scope
This error affects all versions of Microsoft 365 / Exchange Online. It does not apply to on-premises deployments of Exchange Server unless the organization is using hybrid configurations where messages are routed between on-premises servers and Exchange Online. The issue can occur in any tenant configuration that involves email routing through Exchange Online or when users attempt to send emails to addresses managed by Exchange Online.
Where To Look First: Logs and Event IDs
To diagnose the root cause of this error, you should start by examining the logs available within the Microsoft 365 admin center. Specifically, navigate to
admin.microsoft.com > Exchange admin center > Mail flow > Message trace. Here, you can filter message traces based on specific criteria such as sender or recipient email addresses and date ranges.
Additionally, inspect NDR emails that are sent back to the original sender when a delivery failure occurs. These emails contain detailed information about why the message could not be delivered, including the exact error string "550 5.2.0 RESOLVER.ADR.InvalidInSmtpAddress".
For more technical details, you can also review Exchange Online Protection (EOP) logs which are available through the same admin portal under
Exchange admin center > Security & compliance > Message trace. Look for log entries that contain the exact error string "550 5.2.0 RESOLVER.ADR.InvalidInSmtpAddress".
Root Causes
Recipient Mailbox is Disabled or Soft-Deleted
If a user's mailbox has been disabled or soft-deleted, Exchange Online will return this error when attempting to deliver messages to that address. To identify if the issue stems from a disabled or deleted mailbox, check the status of the recipient in the Microsoft 365 admin center under
Users > Active users. If the user is listed but marked as "Disabled" or appears in the list of soft-deleted mailboxes within the Exchange admin center under
Recipients > Mailboxes > Deleted mailboxes, you can take appropriate actions to restore the mailbox.
Duplicate or Invalid SMTP Proxy Address on Recipient Object
Another common cause is when a recipient object (user, group) has duplicate or invalid SMTP proxy addresses. This can occur during migrations from on-premises environments where old addresses might still be present but not properly removed before MX cutover. To verify the validity of SMTP proxy addresses, use the following PowerShell cmdlet:
Get-Mailbox -Identity | Select EmailAddresses
This command will list all email addresses associated with a user or group and help you identify any issues.
Distribution Group SMTP Address Misconfiguration
Distribution groups may have their SMTP address misconfigured, leading to this error. Ensure that the distribution group's primary SMTP address is correctly set up and matches what users are trying to send messages to. You can check and modify these settings via the Exchange admin center under
Recipients > Groups.
Address Rewrite Rule Creating an Invalid Address
Sometimes, transport rules or connector configurations might inadvertently create invalid addresses during message routing. Review any address rewrite rules by running:
Get-TransportRule | Where-Object {$_.State -eq "Enabled"}
This will help you identify and correct any problematic rules that could be causing the issue.
Fix Procedure
To resolve this error, follow these steps:
1. **Check Recipient Status**: Navigate to
Exchange admin center > Users > Active users. If the recipient is disabled or soft-deleted, proceed with restoring it.
2. **Restore Soft-Deleted Mailbox**:
- Go to
Exchange admin center > Recipients > Mailboxes > Deleted mailboxes.
- Select the mailbox and choose "Restore" from the actions menu.
3. **Verify SMTP Proxy Addresses**: Use PowerShell to check for any invalid or duplicate proxy addresses.
Get-Mailbox -Identity | Select EmailAddresses
4. **Run Post-Migration Checks**:
If this error occurs after a migration, run the following command to ensure that all necessary services are available and correctly configured.
Test-MigrationServerAvailability
5. **Review Distribution Group Settings**: Ensure that distribution groups have their primary SMTP address set up correctly.
6. **Address Rewrite Rules Review**:
Use PowerShell to review transport rules for any unintended address modifications.
Get-TransportRule | Where-Object {$_.State -eq "Enabled"}
Error Code Variants
| Error Code |
Description |
Distinguishing Features |
| 550 5.1.3 RESOLVER.ADR.RecipientNotFound |
The recipient address is not found in the directory. |
This error occurs when there's no matching entry for the recipient, while "RESOLVER.ADR.InvalidInSmtpAddress" indicates issues with the format or status of an existing address. |
| 550 5.1.2 RESOLVER.ADR.RecipientNotAllowed |
The recipient is not allowed to receive messages from the sender. |
This error relates to permission issues rather than addressing format or status problems like "RESOLVER.ADR.InvalidInSmtpAddress". |
Verification
After implementing fixes, verify that the issue has been resolved by checking for the absence of NDR emails with the error string "550 5.2.0 RESOLVER.ADR.InvalidInSmtpAddress". Additionally, confirm through message traces in the Exchange admin center that messages are now being delivered successfully to the intended recipients.
Prevention