An S3150 bounce means Outlook.com has blocked the IP address your mail came from, or the range it sits in, so every message to outlook.com, hotmail.com, live.com and msn.com addresses is refused. Stop sending to those domains, fix whatever could be producing spam from that IP, then submit Outlook.com's sender support request and reply to the automated answer if you need a person to look at it. If you send through a hosting provider or email service, it is their IP: ask them to deal with it.
This is a receiving-side block at Microsoft's consumer mail service. It is different from Microsoft 365 refusing to send your mail, which uses codes such as 550 5.7.708. Both are covered in our SMTP error codes guide for cold email.
The full bounce and what each part means
A typical S3150 rejection, as posted on Microsoft Q&A (IP changed to a documentation address):
550 5.7.1 Unfortunately, messages from [198.51.100.40] 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. [VE1EUR01FT080.eop-EUR01.prod.protection.outlook.com 2024-02-02T21:37:21.315Z 08DC2164772DB05A]
| Part | Meaning |
|---|---|
550 5.7.1 | Permanent policy rejection: "Delivery not authorized, message refused" in RFC 3463 terms |
messages from [198.51.100.40] | The IP that connected to Outlook.com. This is what is blocked, not your domain or address |
| "contact your Internet service provider" | Microsoft assumes the IP belongs to an ISP or host, not to you |
| "part of their network is on our block list" | The block may cover a range, not only your single address |
(S3150) | Microsoft's internal block reference |
| Bracketed server and timestamp | The Outlook.com server and time of rejection; include this in a support request |
Note what the bounce does not say. It does not mention content, authentication or your domain. Changing the From address or the wording of your emails will not help while the IP stays listed.
S3150 versus S3140
Microsoft does not publish definitions for these codes; its postmaster troubleshooting page lists other families (RP, SC, DY, OU) but not S3140 or S3150. The most useful public description comes from hosting providers. Hetzner's documentation describes:
| Code | Behaviour described by Hetzner | What to do |
|---|---|---|
| S3150 | A per-IP throttle that clears automatically after a few days if no more mail goes to Outlook.com accounts | Stop sending to Outlook.com, fix the cause, request delisting if it persists |
| S3140 | An older block that does not clear on its own | Fix the cause and request delisting |
Twilio SendGrid's support article treats the two together and notes that many of these blocks clear on their own. Either way, the first step is the same: stop the traffic that is still hitting the block.
Why shared hosting ranges get blocked
S3150 bounces often reach people who have sent very little mail. Typical reasons:
- Inherited reputation. Cloud and dedicated server IPs are reused. The previous tenant of
198.51.100.40may have sent spam. - Neighbours. "Part of their network" means Microsoft may have listed a range because of other addresses in it.
- Shared web hosting. Every site on the server sends through the same IP. One compromised WordPress contact form sending thousands of messages blocks everyone.
- A compromised mailbox or script on your own server. Check before you blame the neighbours.
- Dynamic or residential IPs. Outlook.com says it "generally does not accept email from dynamic IP's" (DY-001). Sending direct from a home connection is never going to work.
A community answer on the Microsoft Q&A thread puts it plainly: S3150 is often about the range, and some senders on affected ranges report having to request mitigation repeatedly.
What to change before asking for delisting
A delisting request that changes nothing tends to be refused, or the block comes back. Work through this list first:
- Reverse DNS. The IP has a PTR record pointing to a hostname, and that hostname resolves back to the same IP.
- Authentication. SPF includes the IP; DKIM signs for your From domain; a DMARC record exists. Outlook.com requires all three for senders of more than 5,000 messages a day (see Outlook.com high-volume sender rules).
- Not an open relay. Your server only relays for authenticated users. Outlook.com lists "open proxy/relay" as a separate reject reason (SC-003).
- Outbound queue. No unexplained messages queued to many recipients; no forms or scripts sending unexpected mail.
- Other blocklists. Check major public lists such as Spamhaus. If you are listed there too, fix that first; the SMTP error code lookup explains a Spamhaus bounce.
- List hygiene. Remove addresses that bounced as unknown. Outlook.com treats probing for valid addresses as "namespace mining" (SC-002).
- Volume. Plan a lower, steadier rate for Outlook.com once unblocked.
Register for SNDS and JMRP
If you control the IP (a dedicated server or a dedicated IP from your provider), sign up for Microsoft's tools before you submit the request. They show you what Microsoft sees.
Smart Network Data Services (SNDS) "gives senders access to detailed data about individual IPs". To use it:
- Sign in at the SNDS site with a Microsoft account.
- Request access to your IP or range.
- Complete the authorisation. SendGrid's guidance describes choosing the
abuse@address for your reverse-DNS domain and clicking the approval link sent there, so make sure that mailbox exists and is read. - Access lasts a limited time: Microsoft says network access "expires 10 months after approval".
Junk Mail Reporting Program (JMRP) is part of SNDS and "lets you receive reports when users junk your messages". Enrol the same IPs. Each report is a recipient who did not want your email; suppress them. Outlook.com says complaint-driven blocks (SC-004) are addressed by enrolling in JMRP and removing complaining recipients.
The delisting request, step by step
S3150 is an Outlook.com consumer block, so the route is Outlook.com's sender support request form, linked from the Outlook.com postmaster site's Support link. Hetzner's documentation gives the form address as https://olcsupport.office.com/ and notes you need a free Microsoft account.
Do not confuse it with https://sender.office.com/, the delist portal for Microsoft 365 (Exchange Online Protection) bans such as 550 5.7.606 Access denied, banned sending IP. Some community answers point S3150 senders there; it is the wrong system for this code.
- Open the form and sign in.
- Enter the blocked IP exactly as it appears in the bounce.
- Paste a recent bounce in full, including the bracketed server name and timestamp.
- Describe your mail honestly and briefly: who you are, what kind of mail the IP sends, roughly how much per day, how recipients came to be on your list, and what you have just fixed.
- Submit, and keep the ticket number.
Expected replies
Hetzner describes the pattern most senders see:
- An automated reply within a few hours. It often says nothing was detected, or that the IP is not qualified for mitigation.
- If so, reply to that email with the requested information and the fixes you made. Hetzner says this escalates the ticket to a member of staff who can delist the IP manually.
- If the IP was recently allocated to you, ask your provider for written confirmation of the allocation date and include it.
SendGrid adds that first replies are often automated and you may need to follow up more than once. Keep replies short and factual; repeat the IP and the error each time.
Microsoft states that submitting a request does not guarantee delivery. Some blocks are lifted and some are not, in which case the realistic options are to wait for an S3150 throttle to lapse or to send through a different, reputable provider.
If you do not own the IP
If the blocked IP belongs to your web host, your ISP or an email service, you cannot register it in SNDS or meaningfully request delisting. Send the full bounce to your provider's support and ask them to handle it, or move your mail to a provider whose sending IPs are well managed. If you send through Microsoft 365 or Google Workspace mailboxes, S3150 is unusual; check the Received headers to make sure the mail really left through them and not through your web server.
How Map Extract helps
Map Extract's bulk email sender sends through your own SMTP accounts, so it does not own or delist any IP. It helps in two practical ways:
- It stops quickly. Replies and bounces are read over IMAP, and the campaign pauses itself when bounces reach the threshold (5% by default). A list with many Outlook.com addresses will trip that before the block gets worse.
- It keeps volume modest. Hourly, daily and monthly caps, per-route ceilings and an optional warm-up ramp keep each sender at a steady, low rate, which is what Outlook.com expects from a small sender.
Uncertain sends are never resent automatically, so a block that interrupts a run does not lead to duplicate messages when you restart. Map Extract does not check blocklists, register SNDS or submit delisting requests for you.
Key takeaways
- S3150 blocks the sending IP or its range at Outlook.com; content and From address changes will not help.
- Hosting documentation describes S3150 as able to clear after a few quiet days, and S3140 as needing a request.
- Fix PTR, authentication, open relay, queue and list problems before asking for delisting.
- Use Outlook.com's sender support form, not the Microsoft 365 delist portal, and reply to the automated answer to reach a person.
- Register your IPs in SNDS and JMRP so you can see the next problem coming.
Frequently asked questions
What does S3150 mean in an Outlook.com bounce?
S3150 is an Outlook.com block on the IP address your mail came from, or on the network range it belongs to. The bounce says part of the network is on Microsoft's block list, so a neighbouring address on the same hosting range can be the cause. It affects mail to outlook.com, hotmail.com, live.com and msn.com addresses, not Microsoft 365 business mailboxes.
How do I get removed from the Outlook S3150 block list?
Fix anything that could be generating spam from the IP first, then submit Outlook.com's sender support request form with the IP address, a copy of the bounce and a short description of your mail. The first reply is usually automated. If it says nothing was found or the IP does not qualify, reply to the same ticket with more detail to ask for a manual review.
What is the difference between S3140 and S3150?
Microsoft does not publish separate definitions. Hosting provider documentation describes S3150 as a block that can clear on its own after a few days if no further mail reaches Outlook.com from the IP, and S3140 as an older style of block that does not clear by itself and needs a delisting request. Treat both as a reason to stop sending and investigate.
Why is my IP blocked by Outlook when I have not sent spam?
Because the block can cover more than your IP. On shared hosting or a cloud provider, the address may have been used by someone else before you, or neighbouring addresses in the same range may be sending spam. A compromised website form or mailbox on your own server is the other common cause. Check your outbound queue and logs before assuming it is someone else.
Sources
Written by the Map Extract editorial team. Found an error? Email support@mapextract.uk and we will check and correct it. How we research guides: editorial policy.