Send & Receive Issues

Fix Exchange Online 550 5.7.501 Errors Caused by a Spamhaus-Listed IP

Aamir Naveed AkramAamir Naveed Akram Nov 20, 2026 869 views

Question details

Identify and resolve a sending IP block that causes Exchange Online to reject mobile users' messages.

Fix Exchange Online Spamhaus IP Blocking and 550 5.7.501 Errors
Product
Exchange Online
Device & OS
not provided
Scenario
A mobile user sends email through Exchange Online while the sending client IP address is blocked by Spamhaus.
Observed behavior
The sender receives a 550 5.7.501 non-delivery report, and a transport rule to remove X-Originating-IP does not prevent the rejection.
Before you start

Collect the non-delivery report and the approximate time of the failed message. You will need Exchange admin access to review the message trace and transport rule.

Solution 1Recommended

Check and Resolve the Sending IP Address Listing

Use this approach when Exchange Online rejects a message because the sending client IP is blocked.

The IP check occurs before the transport rule runs, so removing X-Originating-IP with a rule will not resolve this rejection.

1
Review the failed message

In the Exchange admin center, go to Mail flow > Message trace and find the failed message. Review its events alongside the 550 5.7.501 non-delivery report.

2
Remove the header-removal rule

In the Exchange admin center, go to Mail flow > Rules and disable or delete the rule created to remove X-Originating-IP. Check whether the rule performs any other necessary actions before removing it.

3
Identify the sending IP

Check the non-delivery report for the sending IP. If it is not available there, ask the user or network administrator to identify the public IP used by the mobile device at the time of sending, including any VPN or mobile carrier connection.

4
Check Spamhaus

Use the Spamhaus IP and Domain Reputation Checker to look up the public IP address. If it is listed, follow the listing's instructions to investigate the cause and request removal, or ask the ISP, mobile carrier, or VPN provider to do so for a shared IP.

5
Retry and escalate if needed

After the listing is resolved, send a test message from the affected connection. If the IP is not listed or the error continues, provide the non-delivery report and message trace details to Microsoft support.

Check and Resolve the Sending IP Address Listing
Shared IP addresses: A mobile carrier or VPN may use a shared public IP that the sender cannot delist directly. Contact the network provider if Spamhaus directs you to the IP owner.
Free Microsoft Office alternative

Work on Office Files With WPS Office

WPS Office is a free, lightweight alternative for working on documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format compatibility make it easy to move existing files. It does not resolve Exchange Online sending errors.

Document IP-block troubleshooting and delisting steps in a WPS documentOpen and edit Microsoft Office formats such as DOCX, XLSX, and PPTXUse familiar editing tools for an easier transitionWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Why doesn't removing X-Originating-IP fix the error?

Exchange Online checks and blocks the IP before the transport rule runs. A rule that removes the header therefore cannot prevent this rejection.

Where can I find the sending IP address?

First check the non-delivery report. If it does not identify the IP, ask the user or network administrator for the public IP used by the mobile device at the time, including any VPN connection.

What if the blocked IP belongs to a mobile carrier or VPN provider?

Look up the IP in the Spamhaus IP and Domain Reputation Checker and follow the listing instructions. For a shared IP, contact the carrier or VPN provider if the IP owner must investigate or request delisting.

What should I do if Spamhaus does not show the IP as listed?

Confirm that you checked the public IP used when the message was sent. If the error persists, contact Microsoft support with the non-delivery report and Exchange Online message trace details.