Home › Exchange Online › 550 5.7.503

Exchange Online · 550 5.7.503 · Exchange Online / Microsoft 365

Exchange Online Error 550 5.7.503: Banned Sender Fix Guide

The error occurs when the sender's IP or domain is blocked by an RBL; resolve by delisting through Microsoft's portal or contacting the RBL owner.

Error Details

FactValueSourceNote
Exact error string550 5.7.503 Access denied, banned sender [<IP>]Exchange Online Non-Delivery Report (NDR)Indicates the sender's IP is blocked
OS buildExchange Online / Microsoft 365Microsoft 365 Admin Center-> Affected service version
Affected serviceExchange Online Protection (EOP)Exchange Admin Centre (EAC) > Mail flow-> Where to check message traces
Delisting URLhttps://sender.office.comMicrosoft Delist Portal-> Submit request here
Potential causeDMARC/SPF/DKIM mismatchOutbound message headers-> Check 'X-MS-Exchange-Organization-SCL' value

Log Files to Check

What This Error Actually Means

The error code 550 5.7.503 Access denied, banned sender [] is raised by Exchange Online Protection (EOP) when an outbound message from a tenant's IP address or domain is rejected due to reputation-based blocking mechanisms. This mechanism evaluates the sending IP against various block lists such as Spamhaus SBL, URIBL, Barracuda RBL, and Microsoft’s Smart Network Data Services (SNDS). The error indicates that the sender's IP has been flagged for spamming activities, leading EOP to reject the message before it reaches its destination. This rejection is a safeguard against potential abuse of email services by malicious actors or compromised user accounts.

Affected Versions and Scope

This error affects all tenants using Exchange Online as part of Microsoft 365 subscriptions. It impacts any outbound email sent from an IP address that has been flagged in reputation-based block lists. Tenants who have strict DMARC policies, use shared IPs for sending emails, or have compromised user accounts may experience this issue more frequently. The error does not affect on-premises Exchange deployments unless they are integrated with EOP and utilize the same IP addresses.

Where To Look First: Logs and Event IDs

To diagnose why an email was blocked due to 550 5.7.503 Access denied, banned sender [], start by examining logs in several locations: Event IDs that are relevant for troubleshooting include:

Root Causes

This section outlines several distinct causes for the 550 5.7.503 Access denied, banned sender [] error:

1. Sender IP Listed in Reputation-Based Block Lists (RBLs)

If your organization's sending IP address is listed in an RBL such as Spamhaus SBL or Barracuda RBL, emails will be blocked by EOP until the listing is removed. To identify this cause, check if other recipients are also receiving NDRs with similar errors from different domains.

2. Compromised User Account Sending Bulk Mail

A compromised user account sending bulk mail can trigger EOP's outbound spam detection mechanisms, leading to IP blocking. Look for signs of unusual activity such as high volumes of emails being sent out in a short period or messages containing suspicious content.

3. DMARC Alignment Failure (SPF/DKIM Mismatch)

If your organization uses DMARC policies and there is a mismatch between SPF and DKIM records, EOP may reject emails from that domain as invalid senders. Check the message headers for the X-MS-Exchange-Organization-SCL header value; if it's >=6, this could indicate a spam detection issue.

4. Tenant on High Risk Delivery Pool (HRDP)

Microsoft may place a tenant in the HRDP due to compliance reasons or suspicious activity patterns. This placement restricts outbound email delivery until further investigation is completed by Microsoft support teams.

Fix Procedure

To resolve the 550 5.7.503 Access denied, banned sender [] error, follow these steps:
  1. Delist IP Address: Visit the Microsoft Delist Portal at https://sender.office.com. Provide necessary details about your organization and request delisting.
  2. Check DMARC Alignment: Use PowerShell to review current SPF, DKIM, and DMARC settings. Execute:
    (Get-DmarcPolicy -Identity "contoso.com").Alignment
    (Get-SpfRecord -DomainName "contoso.com")
    
    Ensure that the alignment matches your organization's requirements.
  3. Review Outbound Connector Configuration: Navigate to Exchange admin center > Mail flow > Connectors. Ensure that all outbound connectors are configured correctly and not routing through non-approved smart hosts.
    Get-RemoteDomain | Select-Object DomainName,SmtpRejectMessagesFromGroups
    
    Adjust settings as necessary.
  4. Contact Microsoft Support: If your tenant is in the HRDP or if delisting does not resolve the issue, contact Microsoft support for further assistance. Provide them with detailed logs and evidence of compliance.
Note: Modifying outbound connector settings can affect email delivery to enrolled devices. Ensure that changes are thoroughly tested before applying them in a production environment.

Error Code Variants

Error CodeDescription
550 5.7.13The sender's IP address is listed in an RBL and the recipient domain has strict policies against such senders.
550 5.7.62Email was blocked due to a DMARC policy failure, indicating that SPF or DKIM checks did not pass for the sender's domain.
550 5.7.41The message was rejected because it originated from an IP address known to be compromised and used in spam campaigns.

Verification

After implementing the fix, verify that emails are no longer being blocked by checking:
TIP: Use the Get-MessageTrace -StartDate (Get-Date).AddHours(-2) -EndDate (Get-Date) cmdlet to quickly review recent message traces for any delivery failures.

Prevention

To prevent recurrence of the 550 5.7.503 Access denied, banned sender [] error: By following these guidelines and best practices, you can significantly reduce the likelihood of encountering this error in your Exchange Online environment.

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.