Error Details
| Fact | Value | Source |
|---|---|---|
| Exact error string | 550 5.7.703 Your message can't be sent because messages to <recipient> are blocked by your organisation's outbound spam filter. | Exchange Online NDR |
| Affected build range | Exchange Online / Microsoft 365 | Microsoft 365 admin center |
| Registry key or OMA-URI involved | N/A - cloud-based service | N/A |
| Relevant service/endpoint URL | https://sender.office.com | Microsoft 365 admin center |
| Log line signature | HostedOutboundSpamFilterPolicy | Exchange Online PowerShell |
Log Files to Check
C:\Program Files\Microsoft\Exchange Server\V15\Logging\MessageTracking\<date>.etl/var/log/exchange/message-tracking.log
What This Error Actually Means
The error code "550 5.7.703 Your message can't be sent because messages toAffected Versions and Scope
This error is applicable to all Exchange Online tenants within Microsoft 365. It does not affect on-premises deployments of Exchange Server unless the organization uses hybrid configurations that integrate with Exchange Online for email delivery. The affected build range includes all current versions of Exchange Online as managed through the Microsoft 365 admin center. It's important to note that this error is specifically tied to cloud-based services and does not involve any local registry keys or OMA-URIs on client devices. Therefore, it applies universally across all tenants using Exchange Online without requiring specific configurations or settings adjustments on individual endpoints.Where To Look First: Logs and Event IDs
To diagnose the root cause of this error, sysadmins should start by examining logs generated by the HostedOutboundSpamFilterPolicy. These can be found in two primary locations: 1. **Local Log File**: C:\Program Files\Microsoft\Exchange Server\V15\Logging\MessageTracking\Root Causes
The error "550 5.7.703" can arise from several distinct causes, each requiring different diagnostic and remediation steps:Tenant-Level Block Applied by Microsoft Due to Spam Complaints
This occurs when Microsoft identifies a high volume of spam complaints against emails originating from your tenant's IP addresses or domains. To distinguish this cause, check the Service Health dashboard for any advisories mentioning spam activity.Sender’s IP Listed on Real-Time Blocklist (RBL)
If an RBL like Spamhaus lists your sending IP address as a source of spam, messages will be blocked according to the HostedOutboundSpamFilterPolicy. You can verify this by checking the status of your tenant's IP at https://sender.office.com.Recipient Domain on Outbound Spam Filter Policy Block List
Administrators may have manually added specific recipient domains to the block list within the outbound spam filter policies in Exchange Online PowerShell or via the admin center. This can be identified by running `Get-HostedOutboundSpamFilterPolicy | FL RecipientLimitExternalPerHour, ActionWhenThresholdReached`.Fix Procedure
To address this issue and restore normal email delivery, follow these steps: 1. **Check Service Health Dashboard**: Navigate to the Microsoft 365 admin center > Health > Service health for any active advisories about Exchange Online delivery.Be cautious when making changes in the admin center as incorrect actions can affect service availability.
2. **Run PowerShell Commands**:
- To check if the sender was auto-blocked: `Get-HostedOutboundSpamFilterPolicy | FL RecipientLimitExternalPerHour, ActionWhenThresholdReached`
- To find any tenant-level sender blocks: `Get-TenantAllowBlockListItems -ListType Sender -Block`
3. **Delist Tenant IP**: Submit the tenant's IP for delisting at https://sender.office.com.
4. **Verify Relay Connector Configuration**:
If using an on-premises relay connecting to Exchange Online, ensure that the relay connector IP matches the source IP in Exchange admin center > Mail flow > Connectors.
5. **Remove Erroneous Sender Blocks**: Use `Remove-TenantAllowBlockListItems -ListType Sender -Ids Error Code Variants
| Code | Description |
|---|---|
| 550 5.7.14 | Your message can't be sent because messages to |
| 550 5.3.0 | The recipient domain is not recognized. |
| 550 5.1.2 | The mailbox you are trying to send to does not exist or the domain name cannot be resolved. |
Verification
To verify that the issue has been resolved, monitor log files for messages no longer being blocked by the HostedOutboundSpamFilterPolicy. Additionally, check the Exchange admin center > Mail flow > Message trace to confirm NDR 5.7.703 errors are no longer appearing.A quick diagnostic shortcut is to use `Get-MessageTrace -StartDate (Get-Date).AddHours(-2) -EndDate (Get-Date)` in Exchange Online PowerShell to review recent message traces.