Home › Exchange Online › 550 5.7.703

Exchange Online · 550 5.7.703 · Exchange Online / Microsoft 365

Exchange Online Error 550 5.7.703 - Outbound Spam Filter Block

Tenant-level block due to spam complaints or compromised accounts; fix involves resolving security issues and requesting removal from blocked list.

Error Details

FactValueSource
Exact error string550 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 rangeExchange Online / Microsoft 365Microsoft 365 admin center
Registry key or OMA-URI involvedN/A - cloud-based serviceN/A
Relevant service/endpoint URLhttps://sender.office.comMicrosoft 365 admin center
Log line signatureHostedOutboundSpamFilterPolicyExchange Online PowerShell

Log Files to Check

What This Error Actually Means

The error code "550 5.7.703 Your message can't be sent because messages to are blocked by your organisation's outbound spam filter" is raised by the Exchange Online service when it detects that an email from a tenant is being flagged as potential spam or malicious activity. This error signifies that Microsoft has automatically placed the sending tenant in a high-risk delivery pool due to detected spam complaints, compromised accounts, or explicit blocking actions taken by administrators within the organization's outbound spam filter policies. The component responsible for raising this error is the HostedOutboundSpamFilterPolicy, which enforces rules and thresholds designed to prevent the spread of spam and malicious content from Microsoft 365 tenants. When these policies are triggered, they block outgoing emails that match certain criteria, such as being sent from an IP address listed on a real-time blocklist (RBL) or originating from a tenant with a high volume of complaints.

Affected 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\.etl 2. **Linux Log File**: /var/log/exchange/message-tracking.log The literal log line to grep for is "HostedOutboundSpamFilterPolicy". Additionally, sysadmins should look into the Microsoft 365 Service Health dashboard in the admin center under Health > Service health for any active advisories about Exchange Online delivery. Event IDs related to this issue include: - **Event ID 1072**: Indicates that a message was blocked by the outbound spam filter policy. - **Event ID 1074**: Provides details on why a specific message was rejected due to spam filtering rules.

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 ` to remove any blocks. 6. **Resolve Compromised Accounts**: If the tenant was auto-blocked due to compromised accounts, reset passwords and enroll in MFA via Entra admin center > Protection > Multifactor authentication. 7. **Open Support Case**: Request removal from the blocked list via Microsoft 365 admin center > Support > New service request.

Error Code Variants

CodeDescription
550 5.7.14Your message can't be sent because messages to are blocked by your organisation's outbound spam filter (different threshold reached).
550 5.3.0The recipient domain is not recognized.
550 5.1.2The 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.

Prevention

To prevent recurrence of this issue, implement the following measures: 1. **Regularly Review and Update SPF Records**: Ensure that your domain's SPF record includes `v=spf1 include:spf.protection.outlook.com -all` to authenticate messages sent through Exchange Online. 2. **Enable DKIM for Domains**: In Exchange admin center > Email authentication, enable DKIM for the affected domains. 3. **Monitor and Respond Promptly to Spam Complaints**: Regularly check the Microsoft 365 Message Center (admin.microsoft.com > Health > Message center) for any compliance or security advisories about outbound mail changes. By adhering to these guidelines and regularly monitoring your environment, you can minimize the risk of encountering this error and maintain reliable email delivery across your organization.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.