About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
The bounce reads: "550 5.7.1 Unfortunately, messages from [IP address] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3150). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors." The sender is Outlook.com (Hotmail, Live and MSN addresses), and, going by the bounce text, it has refused mail from your server's IP address. Microsoft's pages do not define S3150.
Fix order: confirm which address Outlook.com saw, check that the sending host meets Microsoft's published requirements, ask your hosting or network provider to look at the block, and submit a removal request through the Outlook.com delisting form. Microsoft does not say how S3150 listings arise, so fix anything the checks below find before you submit.
What the error means
The bounce wording, as quoted in Microsoft Q&A user posts, says two things: the rejection is about the sending network, not about the content of one message, and the owner of that network (your ISP or hosting provider) is the party Microsoft expects to act.
Microsoft's own documentation is thin on this code. The Outlook.com Postmaster site has a table of SMTP error codes. S3150 is not in that table. The S3150 bounce text itself appears in posts on Microsoft Q&A, a user-to-user forum. Treat what those posts say about causes as user reports, not as Microsoft statements.
The Postmaster pages do document the conduct Outlook.com expects of senders. That is the checklist to act on.
Likely causes
Microsoft does not say how S3150 listings arise. Row 1 rests on user posts on Microsoft Q&A; rows 2 to 5 are general sender requirements from the Postmaster pages, which do not mention S3150.
| Cause | What you see | How to confirm |
|---|---|---|
| The IP, or a neighbouring range at your provider, is on the block list, as the bounce says | Only Outlook.com, Hotmail and Live recipients bounce; other providers accept | Your server's public sending IP matches the address in the bounce; ask the provider whether other customers on the range have been blocked |
| The sending IP is new and has no sending history | Problems from the first days; the server is new or the IP is new | Age of the IP; Microsoft's note that "emails from new IPs are more likely to experience deliverability issues" |
| The IP looks like dynamic or residential space | Mail sent directly from an office or home connection | Microsoft's policy: "Connections from dynamic IP space may not be accepted" |
| No valid reverse DNS | The sending address has no matching PTR record | Check the PTR record for the IP; policy: "Email servers must have valid reverse DNS records" |
| Mail is sent through an insecure relay or proxy, or the server was abused | Spam in the queue, unknown senders, open relay | Policy: "Messages must not be transmitted through insecure email relay or proxy servers"; read the queue and logs |
| The sending address is a different one from what you expect | A NAT, a proxy or a relay changed the visible IP | Compare the IP in the bounce with the address your server uses to send |
Prove the cause before changing anything
Everything here is read-only.
1. Take the IP address from the bounce. Compare it with the public address your server uses to send. If they differ, you are looking at the wrong host: a smarthost, a firewall translation or a relay is sending for you, and that is the address Microsoft listed.
2. Check the Microsoft requirements, one at a time. The Postmaster Policies page lists technical requirements for servers connecting to Outlook.com, including:
- the sender must follow the IETF standards for Internet email;
- after a 5xx response, the sender must not retry that message to that recipient, and after multiple non-delivery responses must stop sending to it;
- no more than 500 simultaneous connections without prior arrangement;
- "Messages must not be transmitted through insecure email relay or proxy servers";
- "Connections from dynamic IP space may not be accepted";
- "Email servers must have valid reverse DNS records";
- no "namespace mining", which Microsoft defines as verifying addresses without sending mail to them.
The Troubleshooting page adds a warning about private addresses: Outlook.com "may not accept email from senders who fail a reverse-DNS lookup", and "IP addresses that are reserved for private (non-routable) networking are ... 192.168.0.0 - 192.168.255.255, 10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255". The page also prints that last range as 172.16.0.0/11; the range it spells out is a /12. It asks too whether anti-virus on your firewall or SMTP server has "Internet Email Auto Protect" or "Internet Email Protection" enabled, which it says can cause delivery trouble.
3. Check sender authentication and volume. Microsoft states that "domains sending more than 5,000 emails per day to Outlook.com accounts must fully be compliant with SPF, DKIM, and DMARC", and that failing messages go to the junk folder and, if unresolved, may be rejected with "550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level." That is a different code from S3150, but a sender with S3150 and failing authentication has two problems. "Application Email Rejected or Junked After a Server Move: SPF, DKIM, DMARC and PTR" covers authentication.
4. Read your own mail log for the day the bounces began. Look for a sudden change in outbound volume, unfamiliar senders or recipients, or a burst of bounces from other providers. A compromised website or account that sent spam can get an IP listed.
5. Ask your provider. The message tells you to: "Please contact your Internet service provider since part of their network is on our block list." Send your provider the exact bounce text, the time, and the IP address, and ask whether the range is known to be listed and whether they have submitted a removal.
Example (illustrative): mail01 (198.51.100.40) is a Postfix server hosted at a provider. After a move, invoices to Hotmail and Outlook.com addresses bounce with the S3150 text, while Gmail and corporate recipients accept. The IP in the bounce is mail01's own address. It has a PTR record, it relays only for the application server, and the mail log shows nothing unusual. Nothing on the server's side explains the listing. The bounce text names the provider's network as the listed party, so the provider is the first contact, before a removal request is sent.
Fix
Ask Microsoft to remove the block
Microsoft documents routes on its own pages. Start with the one its Learn page assigns to Outlook.com.
- Outlook.com delisting form (first route). The Microsoft Learn page "External senders - Use the delist portal to remove yourself from the blocked senders list and address 5.7.511 Access denied errors" (no date shown in the page text; its metadata lists 2024-06-10 and an update on 2026-06-01) says, under "More information": "The delisting form for Outlook.com, the consumer service can be found here. Be sure to read the FAQ first for submission direction." The link leads to a Microsoft support request form that asks you to sign in. The S3150 bounce comes from Outlook.com, the consumer service, so this is the route that page documents for it. Read the Postmaster Troubleshooting page (the FAQ link) first, and send the IP address and the exact bounce text.
- Outlook.com Deliverability Support. The Postmaster Policies page says: "If you are adhering to the guidelines, practices and policies presented on this page and are still experiencing deliverability issues, please contact Outlook.com deliverability support. If you are not in compliance with the above policies and guidelines, it may not be possible for our support team to assist you." The link is a go.microsoft.com redirect that, when requested on 19 November 2026, ended at a Microsoft sign-in page returning to olcsupport.office.com. The Troubleshooting page says that submissions "should only be related to the Outlook.com system" and that "submitting this information does not guarantee that any message you send to users of the Outlook.com services will be delivered."
- Office 365 Anti-Spam IP Delist Portal (for Microsoft 365 recipients). The Learn page says the portal is "for external message senders" to request removal from the blocked senders list, and the portal page says: "If you're trying to send mail to an Office 365 recipient and the mail has been rejected because of your sending IP address, follow these steps to submit a delisting request. Senders are responsible for making sure that their mail from this IP address isn't abusive or malicious." The form asks for an email address and the IP address, and confirms the address in a second step. One user post from May 2026 says the confirmation email from the portal never arrived for an S3150 block, after several tries.
The Learn page gives delist@microsoft.com only for the 5.7.511 error, not for S3150.
Risk: a removal request does not repair the cause, and the block can return if the cause persists. No page read says how many requests per block are accepted, so wait for a reply before you try again. No page read describes withdrawing a submission, so there is no back-out.
Fix the cause Microsoft's pages describe
- Correct reverse DNS, remove any path through an open relay or proxy, and stop mail from compromised accounts or sites.
- If the IP is new, expect a ramp-up. Microsoft says "a new IP can expect to be fully ramped within a couple of weeks or sooner depending on volume, list accuracy and as long as their junk email complaint rates are kept at a minimum."
- Enrol the IPs in Microsoft's free tools. The Services page describes the Junk Email Reporting Program (JMRP), which "returns select message headers for emails marked as 'junk'", and Smart Network Data Services (SNDS), which gives "high-level insight on how users are rating the email they receive and the health of your IP space as viewed by the Outlook.com system".
- If another range at your provider is the problem, that is for the provider to resolve with Microsoft.
If the block will not clear: use another sending path
Risk: moving outbound mail to an authenticated relay on a different network changes the visible IP, so SPF, reverse DNS and any allow-lists at the recipients must match the relay, or you create a new set of failures. Test with a few messages first, and keep the old path configured so you can switch back. See "Outbound mail times out after a move: the new host cannot reach port 25" for how relay submission works.
Microsoft states that Outlook.com has no allow list ("No. An 'allow list' is essentially a 'free pass' ..."), so there is nothing to ask for beyond removal.
Confirm the fix
- Send a test message from the same server to an Outlook.com address and read the response. The response to that message shows whether the rejection remains.
- Check the queue and the mail log for the S3150 text; it should stop appearing.
- Watch for a few days. Microsoft notes new IPs build reputation gradually, and a removal may not last if the cause persists.
- Ask a recipient to confirm that the message arrives in the inbox, not only that it is accepted.
What to watch afterwards
- Repeat the test to an Outlook.com address weekly, and alert on any 5.7.1 response.
- Keep SPF, DKIM and DMARC passing, because Microsoft enforces them for high-volume senders.
Read next
Related articles you may want next.
- HostingApplication Email Rejected or Junked After a Server Move: SPF, DKIM, DMARC and PTRApplication mail bouncing or junked after a migration? Read Authentication-Results, then fix SPF, DKIM, DMARC alignment, PTR and Microsoft 365 relay settings for the new path.Read article
- TroubleshootingOutbound mail times out after a move: the new host cannot reach port 25Mail queued and port 25 times out after moving to Azure, AWS or Google Cloud? Prove the block with a TCP test and switch to an authenticated relay.Read article
- Troubleshooting554 5.7.1 Client host blocked using zen.spamhaus.org: which list, and how to get off itMail rejected: Client host blocked using zen.spamhaus.org? Check the ZEN return code, work out SBL, CSS, XBL or PBL, and take the right removal route.Read article
Risks and limits
- Microsoft does not document S3150 in the Postmaster code table read here. The meaning "your IP, or a range at your provider, is on Microsoft's block list" comes from the text of the bounce itself. Explanations of why a given IP was listed come from user posts and cannot be verified from Microsoft's pages.
- The delist portal is described by Microsoft for Office 365 recipients. Whether it clears an Outlook.com S3150 block is not stated in the pages read, and one user post reports the confirmation email never arriving.
- The Outlook.com delisting form and the Deliverability Support form require a Microsoft sign-in and were not readable without one, so their fields are not described.
- The link inside the bounce (mail.live.com/mail/troubleshooting.aspx#errors) led to the Postmaster front page on 18 November 2026, not to a page about block lists.
Sources
- Outlook.com Postmaster: Troubleshooting — Microsoft, footer "2025 Microsoft", accessed 18 November 2026
- Outlook.com Postmaster: Policies, Practices, and Guidelines — Microsoft, footer "2025 Microsoft", accessed 18 November 2026
- Outlook.com Postmaster: Services for Senders and ISPs — Microsoft, footer "2025 Microsoft", accessed 18 November 2026
- Office 365 Anti-Spam IP Delist Portal — Microsoft, footer "2026", accessed 18 November 2026
- External senders - Use the delist portal to remove yourself from the blocked senders list and address 5.7.511 Access denied errors — Microsoft Learn, no date shown in the page text (metadata: 2024-06-10; update 2026-06-01), accessed 18 November 2026
- Microsoft Q&A: How to I contact Microsoft about Block List S3150 — Microsoft Q&A, question posted 17 February 2026 (accepted answer 18 February 2026), accessed 18 November 2026
- Microsoft Q&A: IP blocked S3150, delist tool not sending confirmation emails — Microsoft Q&A, user post of 26 May 2026, accessed 18 November 2026
- Microsoft Q&A: What does error "S3150" mean? — Microsoft Q&A, question posted 2 February 2024, accessed 18 November 2026
This article was originally published on .