Send & Receive Issues

Fix Microsoft 365 Error 550 5.7.511 for a Banned Sender

Amos GikundaAmos Gikunda Nov 20, 2026 869 views

Question details

Restore delivery from a private VPS mail server to Microsoft 365 recipients after a banned-sender rejection.

Product
Microsoft 365 and Exchange Online
Device & OS
not provided
Scenario
A private VPS mail server sends messages to recipients hosted by Microsoft 365.
Observed behavior
Microsoft 365 rejects messages with error 550 5.7.511. The sending IP is not on common public blacklists, and a delisting request has not resolved the rejection.
Before you start

Collect the complete non-delivery report, the public sending IP address, and the timestamps of recent rejected messages. Confirm which server or relay actually sent the messages to Microsoft 365.

Solution 1Recommended

Check Sender Authentication and Request Microsoft IP Delisting

Use this approach to verify the sending server's configuration and submit its public IP for review.

1
Review the rejection

Open the non-delivery report or mail server log and identify the public sending IP, the full 550 5.7.511 response, and the time of the rejection.

2
Check reverse DNS

Use a DNS lookup tool to check the sending IP's PTR record. Confirm that it resolves to a valid hostname and that the hostname resolves back to the sending IP; ask your VPS provider to update the PTR record if necessary.

3
Verify email authentication

Check your domain's DNS records for SPF, DKIM, and DMARC. Confirm that SPF authorizes the actual sending server, DKIM signing works, and at least one authenticated domain aligns with the From address for DMARC.

4
Request delisting

Go to https://sender.office.com, enter a contact email address and the sending IP, and follow the verification and delisting instructions sent by the portal.

5
Test delivery again

After completing the request, send a test message to a Microsoft 365 recipient and check the mail log or non-delivery report for the result. Allow more than 48 hours for a request to be processed.

Public blacklist status is not conclusive: An IP can be absent from common public blacklists and still be blocked by Microsoft. A delisting request also does not guarantee delivery.
Free Microsoft Office alternative

Use WPS Office for Microsoft Office-Compatible Documents

WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations in a familiar interface. It supports common Microsoft Office formats for easier migration, but it does not remove Microsoft 365 sender blocks.

Create and edit documents while Microsoft investigates the mail delivery issueOpen and save common Microsoft Office formats, including DOCX, XLSX, and PPTXUse a familiar interface for everyday office workGet a lightweight office suite with free features
microsoft office alternative - wps office

Frequently Asked Questions

Why is Microsoft blocking my IP when it is not on public blacklists?

Microsoft uses its own sender protection systems, so a clean result on a public blacklist does not rule out a Microsoft block. Check the rejection details and submit the sending IP at https://sender.office.com.

What if sender.office.com says my IP is not blocked?

Confirm from the mail server logs that you submitted the public IP that actually sent the rejected message. If it is correct and the error continues, contact Microsoft support with the full rejection, timestamps, and IP address.

How long does Microsoft 365 delisting take?

Processing can take more than 48 hours. Complete the instructions sent by sender.office.com, then test delivery and contact Microsoft support if the rejection persists.

Which DNS records should I check for the sending server?

Check the sending IP's PTR record and the domain's SPF, DKIM, and DMARC records using a DNS lookup tool. SPF should authorize the sending server, and DMARC requires alignment with the From domain through SPF or DKIM.

What information should I send to Microsoft support?

Provide the complete non-delivery report, relevant message headers, public sending IP, timestamps with time zones, and any delisting request details. Include a recent failed test if the issue is still occurring.