Sending, receiving, and organizing email in Outlook on the web for business
Submit the affected public outbound IP and complete S3150 bounce message through the Outlook.com Sender Support troubleshooting form; do not post the server IP publicly in this Q&A thread.
Request an Outlook.com/Hotmail review
S3150 indicates that Microsoft’s consumer mail service is rejecting mail associated with the outbound sending IP or its network. For failures involving @outlook.com, @hotmail.com, @live.com, or @msn.com:
- Preserve the complete non-delivery report (NDR), including:
- The full
550 5.7.1 ... (S3150)response. - The public outbound IP shown in the response.
- Sending and recipient domains.
- UTC timestamp and message ID, if present.
- The full
- Open the Outlook.com Sender Support troubleshooting form linked under Sender services, tools, and issue submission in Microsoft’s sender guidance.
- Enter the affected outbound IP and paste the complete NDR.
- Describe the issue as “S3150 rejection—request for mitigation review.”
- Submit one representative case and retain its confirmation or ticket number.
This form is specifically for deliverability to Microsoft’s consumer domains. Submission starts a review but does not guarantee delivery.^1^
Only provide the IP in that private form. Microsoft Learn Q&A is a public user-to-user forum and cannot inspect or remove backend blocks.^2^
If the rejected recipient is Microsoft 365 instead
Use this branch only when the NDR is for a recipient hosted in Microsoft 365 and identifies a banned sending IP, commonly with an error such as 550 5.7.606-649.
- Go to the Office 365 Anti-Spam IP Delist Portal: https://sender.office.com/
- Enter:
- The email address that received the NDR.
- The public sending IP specified in the NDR.
- Select Submit.
- Open the verification message sent by Microsoft and follow its confirmation link.
- Return to the portal and select Delist IP.
Microsoft notes that restrictions can take 24 hours or longer to clear.^3^
The Outlook.com sender form and Microsoft 365 delist portal are different paths. Select the path from the rejected recipient’s service and the exact NDR rather than submitting the IP indiscriminately to both.
Prevent the IP from being blocked again
Before or while awaiting review:
- Confirm the public IP has valid forward and reverse DNS; Microsoft may reject senders that fail reverse-DNS lookup.
- Ensure the SMTP
EHLO/HELOpresents a public, resolvable hostname rather than a private IP. - Verify SPF authorizes the actual outbound IP and that DKIM and DMARC pass.
- Review SMTP logs for compromised accounts, unusual volume, recipient enumeration, repeated invalid recipients, or unexpected scripts.
- Stop unsolicited traffic and sudden volume spikes.
- Remove stale or purchased recipient lists and process bounces and complaints promptly.
Microsoft states that reputation considers the sending IP, domain, authentication, list quality, message content, and complaint rates; junk-mail complaints are a major deliverability factor.^1^
If the organization does not own the outbound IP—for example, it belongs to an ISP, hosting provider, relay service, or shared mail platform—the IP owner should submit the review and investigate other traffic using that address. Microsoft also recommends following the NDR instructions and, for unresolved Microsoft 365 delivery cases, asking the Microsoft 365 recipient’s administrator to open a support ticket.^4^
References