Fix an Office 365 Email Blocked by a Spamhaus 550 Error
Question details
Determine why an Office 365 email is blocked by a Spamhaus-related 550 error and restore sending.

- Product
- Microsoft 365 Exchange Online
- Device & OS
- not provided
- Scenario
- An Office 365 user cannot send email because an SMTP rejection references Spamhaus.
- Observed behavior
- The message receives a 550 error even though the sending IP address may not appear on a public Spamhaus list.
Keep the complete nondelivery report (NDR), including the SMTP error and message headers. Ask a Microsoft 365 administrator with the appropriate permissions to check the sending account.
Check and unblock a restricted Exchange Online sender
Use this approach when Microsoft 365 may have restricted the sending account.
Sign in to the Microsoft Defender portal at security.microsoft.com as an administrator. Go to Email & collaboration > Review > Restricted entities.
Find the affected account in the restricted entities list and open its details to review the restriction.
If the account is restricted, investigate suspicious activity and secure the account first. Then select the account and use Unblock, following the portal prompts.
Send a new test message from the affected account and check whether it is delivered or generates another NDR.

Review the rejection and contact the appropriate support team
Use the full NDR to identify who rejected the message, especially if the account is not restricted or the error continues.
Work with Office attachments in WPS Office
WPS Office is a free, lightweight alternative with a familiar interface for working with Microsoft Office files. It can help you move existing documents into a new workflow, but it cannot unblock an Exchange Online account or fix a Spamhaus email rejection.

Frequently Asked Questions
Why does the error mention Spamhaus if my IP is not listed?
The rejection may involve a sending account, another sending source, or the recipient's filtering policy. Review the complete 550 response and the rejecting server in the NDR rather than relying on a public IP lookup alone.
Where can an administrator check whether a sender is blocked?
In the Microsoft Defender portal at security.microsoft.com, go to Email & collaboration > Review > Restricted entities and look for the affected account.
Should I unblock the account immediately?
First investigate any suspicious activity and secure the account. Once the cause is addressed, an authorized administrator can select the account on the Restricted entities page and use Unblock.
What should I send Microsoft Support if the error continues?
Provide the tenant details, complete NDR, and any existing support request number through the Microsoft 365 admin center's Help & support channel or by replying to the existing support email.




