NetSendo
Guides & Tips

Outlook S3150 block: SNDS, JMRP and how to get delisted

NetSendo Team16 min read
Outlook S3150 block: SNDS, JMRP and how to get delisted

A bounce that ends in "part of their network is on our block list (S3150)" means Outlook.com (the consumer service behind @outlook.com, @hotmail.com, @live.com and @msn.com) refuses mail from your sending IP because of its reputation. It is not a public blacklist, and fixing DNS does not lift it by itself. You check the IP in Microsoft's SNDS portal, fix what caused the listing, then file a mitigation request with Outlook.com sender support, not with the Microsoft 365 delist portal.

TL;DR: S3150 and S3140 come from the Outlook.com consumer filter; 5.7.606 and 5.7.511 come from Microsoft 365, and each has its own removal path. Register your IPs in SNDS to see filter verdicts, complaint rates and block status, and enrol them in JMRP to receive a copy of every message Outlook.com users mark as junk. Before you ask for removal, make sure the IP has a matching PTR record, the From domain passes SPF, DKIM and DMARC, and complainers are suppressed. Then submit the form at olcsupport.office.com and reply to the automated answer to reach a person.

What does S3150 mean in an Outlook bounce?

S3150 means the IP address that connected to Outlook.com's inbound servers is on Microsoft's internal block list for the consumer mail service, so every message from that IP is refused with a permanent 550 error. The full text usually reads:

550 5.7.1 Unfortunately, messages from [203.0.113.10] 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 wording "part of their network" has not changed in years and covers both a single IP and a whole range. Hetzner's documentation describes the current behaviour well: Microsoft has moved away from blocking whole subnets (S3140) and towards per-IP limits that are assigned dynamically and can be very low for IPs that rarely send to Outlook.com; once an IP hits that limit, everything is refused with S3150 (Hetzner Docs, Microsoft Blacklist). According to the same page, an S3150 listing usually expires after a few days if the IP stops sending to Outlook.com, while S3140 does not expire on its own.

Three consequences follow from this:

  • Checking public DNS blacklists will often show nothing. Hetzner notes that Spamhaus is the only external list Microsoft is known to use; everything else is Microsoft's own scoring.
  • Gmail or Yahoo accepting the same mail proves nothing about Microsoft. Each provider scores your IP separately.
  • A new VPS can be blocked on the first day. The IP inherits whatever its previous tenant did, and a low-volume IP has almost no positive history to balance it.

Which Microsoft bounce codes matter and what do they mean?

The code at the end of the bounce tells you which Microsoft system rejected you and which fix applies; read it before doing anything else. Microsoft publishes some of these codes on the Outlook.com postmaster troubleshooting page, while others are only documented by hosting and sending providers.

Code in the bounceSystemTypeWhat it meansWhat to do
550 5.7.1 … (S3150)Outlook.comPermanentSending IP is on the consumer block listFix causes, check SNDS, request mitigation at olcsupport.office.com
550 5.7.1 … (S3140)Outlook.comPermanentBlock covering the IP or its range; does not expire by itselfSame as S3150; ask your hosting provider if a whole range is affected
451 4.7.650 … rate limited due to IP reputation (S775)Outlook.comTemporaryThrottling because of IP reputationSlow down, keep retrying, do not raise volume
421 RP-001 / RP-002 / RP-003Outlook.comTemporaryRate or connection limit exceeded, tied to IP/domain reputationFewer parallel connections and messages per connection
550 SC-001 / SC-002 / SC-003Outlook.comPermanentPolicy rejection: reputation or content, namespace mining, open proxy/relayStop address verification probes, close the relay, then ask support
550 5.7.515 Access denied … does not meet the required authentication levelOutlook.comPermanentHigh-volume From domain fails SPF, DKIM or DMARCFix authentication; no delisting exists for this
550 5.7.606 Access denied, banned sending IPMicrosoft 365PermanentIP on the Microsoft 365 blocked senders listSelf-service delisting at sender.office.com
550 5.7.511 Access denied, banned senderMicrosoft 365PermanentNeeds manual investigationForward the full bounce to delist@microsoft.com

As of November 2026. Sources: Outlook.com postmaster troubleshooting (RP, SC and 5.7.515), Microsoft Learn, delist portal (5.7.606, 5.7.511), Twilio SendGrid (S3140/S3150 and 4.7.650 wording).

To find out how many recipients are affected, search your MTA log for these codes. On a Postfix server:

grep -E 'S3150|S3140|4\.7\.650|5\.7\.515|5\.7\.606|5\.7\.511' /var/log/mail.log \
  | grep -oE '(S3150|S3140|4\.7\.650|5\.7\.515|5\.7\.606|5\.7\.511)' | sort | uniq -c

If you send through a provider such as Amazon SES or Mailgun, the same text appears in their bounce events. On a shared IP pool the listing belongs to the provider, and only the provider can request removal.

Is Outlook.com or Microsoft 365 blocking you?

Look at the recipient and the code: @outlook.com, @hotmail.com, @live.com and @msn.com addresses use the consumer filter (S3150, S3140, 4.7.650), while company domains hosted on Microsoft 365 use Exchange Online Protection (5.7.606, 5.7.511). The two lists are separate, so delisting on one does nothing for the other (Hetzner Docs).

This explains the most common complaint on Microsoft Q&A: "the delist portal says my IP is not blocked, but Hotmail still bounces my mail". The portal at sender.office.com only knows about the Microsoft 365 list. Microsoft's own article on the portal points consumer-service senders to a different form, the Outlook.com sender support form (Microsoft Learn).

SNDS and JMRP

Smart Network Data Services (SNDS) is Microsoft's free portal that shows how Outlook.com sees each IP you control. The Junk Mail Reporting Program (JMRP) is the Outlook.com feedback loop: it sends you a report for each message a user marks as junk. Both cover the consumer service only.

What should you fix before asking for removal?

Fix the cause first, because a delisted IP that keeps sending the same way is listed again, and repeat requests get slower answers. Outlook.com's policies list the technical minimum: valid reverse DNS, no dynamic IP space, no open relays or proxies, no namespace mining, no retries after a 5xx response, and no more than 500 simultaneous connections without prior arrangement (Outlook.com policies).

  1. Check PTR and forward DNS

    The PTR name of the sending IP must resolve back to the same IP, and your MTA should announce that name in HELO/EHLO.

    dig +short -x 203.0.113.10        # expect: mail.example.com.
    dig +short A mail.example.com     # expect: 203.0.113.10
  2. Check authentication of the From domain

    SPF must list the IP, DKIM must sign with the From domain (or a parent of it), and a DMARC record must exist. Send a message to an Outlook.com mailbox you own and read the Authentication-Results header.

    dig +short TXT example.com | grep spf1
    dig +short TXT _dmarc.example.com
    dig +short TXT s1._domainkey.example.com   # replace s1 with your DKIM selector
  3. Stop sending to dead and unconfirmed addresses

    SNDS compares RCPT commands with accepted recipients. Microsoft notes that more than a third of IPs keep the share of RCPT commands that do not turn into recipients under 10% (SNDS FAQ). Old imported lists and SMTP-based address verification push this number up; Microsoft treats the latter as namespace mining.

  4. Bring complaints down

    For reference, Microsoft says more than 30% of sending IPs keep their complaint rate below 0.3%, and calls that a good target (SNDS FAQ). Add a visible unsubscribe link and a one-click List-Unsubscribe header, and stop mailing people who never opened or clicked.

  5. Ramp new IPs slowly

    Microsoft says a new IP can expect to be fully ramped "within a couple of weeks or sooner", depending on volume, list quality and complaint rate, and new IPs under an existing domain's SPF inherit some of that domain's reputation (Outlook.com troubleshooting). Start with your most engaged recipients.

  6. Check for compromise

    A hacked mailbox, a contact form used as a relay or a forgotten WordPress plugin can send spam from your IP without you noticing. Check the queue and log volume per sender before blaming Microsoft.

⚠️ Warning: Do not keep retrying 550 S3150 bounces or rotate to a fresh IP to get around the block. Microsoft's policies require senders to stop after a permanent error, and moving the same list to a new IP usually gets that IP listed as well.

A broader checklist for authentication, warm-up and list hygiene is in our deliverability guide for self-hosted senders, and the details of SPF records that hit the lookup limit are in SPF "too many DNS lookups".

How do you register and read SNDS?

Sign in with any Microsoft account at the SNDS portal, request access to your IP or range, and confirm through an email sent to an address Microsoft finds for that range; data appears from the next daily update. Since 22 September 2026 the portal runs at substrate.office.com/ip-domain-management-snds/snds, replacing the old sendersupport.olc.protection.outlook.com/snds address, and approved access no longer needs periodic reattestation (SNDS announcement).

Getting access

SNDS chooses the authorisation addresses automatically. For an IP or range it looks at reverse DNS: if all sampled PTR names are in one domain, it offers postmaster@ and abuse@ that domain. It also reads the RDAP record of the allocation and offers the contacts listed there. The reverse DNS method works for ranges up to a /23 (SNDS FAQ).

In practice: set the PTR of your server to a name in your own domain (for example mail.example.com), make sure postmaster@example.com or abuse@example.com receives mail, and request a single IP. If you rent a VPS, the RDAP contacts are your provider's, so the PTR route is the one you control. The SNDS team cannot add access manually.

What the data means

SNDS fieldWhat it showsWhat to look for
RCPT commands / DATA commands / Message recipientsRecipients attempted, messages transmitted, recipients accepted per dayA large gap between RCPT and recipients points at stale lists
Filter resultShare of spam verdicts: green < 10%, yellow 10–90%, red > 90%Anything other than green on a list you consider clean
Complaint rateJunk reports ÷ message recipients, counted on the day of the reportAbove 0.3% is worse than the benchmark Microsoft cites
CommentsJMR P1 Sender, JMR Block, JMRP spam complaint count, viruses, open proxy"JMR Block" means the IP is blocked because of complaints
View IP StatusBlocked, Bot or Junked status for the last 24 hoursBlocked IPs get consistent refusals; Junked IPs are heading there

As of November 2026. Source: SNDS FAQ.

Limits to keep in mind: data for a day is aggregated after midnight Pacific time and can take a few hours to appear, it is kept for 90 days, and traffic and spam data may be missing for IPs that sent fewer than 100 messages that day. A small newsletter on its own IP may therefore see an empty data page and still be blocked; the View IP Status page is the one to check. SNDS also offers a CSV export and an automated data URL you can poll from a script. Microsoft states that differences between filter colour, complaint rate and block status are not a bug: filtered mail is seen by fewer users, so it collects fewer complaints.

How does JMRP work and what do you do with the reports?

JMRP sends you an Abuse Reporting Format (ARF) report each time an Outlook.com user marks a message from your IP as junk; you enrol from the "Junk Mail Reporting Program" tab inside SNDS, and reports typically start within 72 hours (Outlook.com services for senders).

The programme is meant for the owner of the sending IP, which is why it only makes sense with a dedicated IP: on a shared pool, the complaints go to the pool's operator. When you add or change IPs, update the JMRP enrolment as well; Microsoft's troubleshooting page reminds senders of this explicitly.

What is in a report

Each report is a multipart/report message as defined in RFC 5965: a short human-readable part, a message/feedback-report part with fields such as Feedback-Type: abuse and Source-IP, and a copy of the original message or its headers. Feedback loops commonly redact the recipient address, so do not rely on the To: header to find the complainer. Put an identifier in the message that survives: a per-recipient unsubscribe URL or a custom header.

The script below reads saved reports (one .eml file each) and extracts the source IP and the subscriber ID from the List-Unsubscribe URL. The pattern matches NetSendo's one-click URL, /unsubscribe/<subscriber id>/<list id>; adjust it to your own system. It was tested with Python 3 on a sample ARF message.

import re
import sys
from email import message_from_binary_file, policy

UNSUB = re.compile(r'/unsubscribe/(\d+)/(\d+)')

def report_field(report, name):
    for part in report.walk():
        if part.get_content_type() == 'message/feedback-report':
            for block in (part.get_payload() if part.is_multipart() else [part]):
                value = block.get(name)
                if value:
                    return value
    return None

def complaint(path):
    with open(path, 'rb') as f:
        report = message_from_binary_file(f, policy=policy.compat32)
    for part in report.walk():
        if part.get_content_type() in ('message/rfc822', 'text/rfc822-headers'):
            original = part.get_payload(0) if part.is_multipart() else part
            match = UNSUB.search(original.get('List-Unsubscribe', ''))
            return {
                'source_ip': report_field(report, 'Source-IP'),
                'subscriber_id': match.group(1) if match else None,
            }
    return None

for path in sys.argv[1:]:
    print(path, complaint(path))

Every complainer should stop receiving marketing mail from you at once, on every list. A junk report is a stronger signal than an unsubscribe: the person did not trust your unsubscribe link, or did not find it.

How do you get an IP off the S3150 list?

For S3150 and S3140, submit the Outlook.com sender support form at olcsupport.office.com (a free Microsoft account is needed), expect an automated reply within hours, and answer that reply to have the ticket escalated to a person (Hetzner Docs).

  1. Collect evidence

    The full bounce with the IP and the S-code, a few timestamps, the sending domain, your SNDS status and the steps you already took (PTR, SPF, DKIM, DMARC, list cleaning).

  2. Submit the form

    Describe the mail honestly: who receives it, how they subscribed, roughly how many messages a day go to Outlook.com addresses.

  3. Read the automated answer

    It often says "Nothing was detected to prevent your mail from reaching Outlook.com customers" or "Not qualified for mitigation". Neither is final. Reply with the requested details and ask for escalation.

  4. Wait for "mitigation"

    When a staff member removes the block, the reply usually says that mitigation has been implemented for your IP. Restart with low volume and engaged recipients.

  5. New IP? Prove it

    If the IP was allocated to you recently and Microsoft still refuses, tell them; they may ask for a confirmation of the allocation date from your hosting provider, which Hetzner, for example, issues on request.

A request text that support staff can act on quickly:

Subject: IP 203.0.113.10 blocked with S3150 – mitigation request

Sending IP:      203.0.113.10 (PTR mail.example.com, matching A record)
Sending domain:  example.com (SPF pass, DKIM d=example.com pass, DMARC p=none aligned)
Mail type:       newsletter to confirmed (double opt-in) subscribers, about 800/day to Outlook.com
Bounce:          550 5.7.1 ... part of their network is on our block list (S3150)
First seen:      2026-11-20 08:14 UTC
SNDS:            IP registered; status 
Actions taken:   removed 1,240 inactive addresses, enrolled in JMRP, one-click unsubscribe added

For Microsoft 365 rejections the path is different. With 5.7.606, open sender.office.com, enter the address that received the bounce and the IP from the error (one of each per visit), confirm the email link and click "Delist IP"; removal can take up to 24 hours or longer. With 5.7.511 the portal cannot help: forward the full bounce to delist@microsoft.com, and Microsoft says it will reply within 48 hours (Microsoft Learn).

✅ When delisting works

  • The IP is new to you and inherited a bad history
  • You found and fixed a clear cause (compromised account, old list)
  • SNDS shows green filter results while S3150 bounces continue

❌ When it will not help

  • The error is 5.7.515: this is an authentication failure, not a listing
  • Complaints stay high: the IP is listed again within days
  • You send through a shared pool: only the provider can file the request

What does Outlook require from senders of 5,000+ messages a day?

Since 5 May 2025, domains that send more than 5,000 messages a day to Outlook.com addresses must pass SPF and DKIM and publish a DMARC policy of at least p=none that aligns with SPF or DKIM, preferably both; non-compliant mail is rejected with 550 5.7.515 (Microsoft announcement, Outlook.com policies).

Microsoft first announced that such mail would go to Junk and later changed the plan to outright rejection with 5.7.515 from the same date. The rule is tied to the domain in the visible From address, not to the IP, so moving to another server does not help. The same announcement lists further expectations: a functional, visible unsubscribe link, valid From and Reply-To addresses, and hygienic lists. Microsoft also says it sends DMARC aggregate (rua) reports, which are a good way to find senders that use your domain without authentication.

A minimal compliant set of records for a domain that sends from its own server and Google Workspace:

example.com.                 3600 IN TXT "v=spf1 ip4:203.0.113.10 include:_spf.google.com ~all"
s1._domainkey.example.com.   3600 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqh..."
_dmarc.example.com.          3600 IN TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

Gmail and Yahoo have comparable rules; the differences are summarised in Gmail 550-5.7.26: causes and fixes and in SPF, DKIM and DMARC explained.

Outlook delivery when you send with NetSendo

NetSendo does not decide whether Outlook.com accepts your mail; the IP and the domain do. What it changes is how much of the setup above you control. When you send through Amazon SES, Mailgun or another SMTP provider configured in NetSendo, the provider owns the IPs, registers them in SNDS and handles delisting. NetSendo sets no sending limits of its own, so volume and pace are up to you and your provider.

With NMI, NetSendo's own mail infrastructure (a GOLD feature), you send from your server's IP or from dedicated IPs, so SNDS and JMRP are yours to set up. The NMI documentation covers the parts that matter for Microsoft:

  • PTR and port 25: Settings → Mailboxes shows whether the server can send, including the PTR check, with step-by-step instructions for Hetzner, OVHcloud, DigitalOcean, AWS and other providers.
  • IP warming: a 28-day schedule that starts at 50–200 messages a day and reaches 80,000–100,000 in the last week (NMI_WARMING_DAYS=28).
  • DKIM per domain: a 2048-bit key generated for each sending domain, plus a DMARC record suggested with p=none.
  • Blacklist monitoring: checks against public DNSBLs such as Spamhaus ZEN and SpamCop every 24 hours by default. Microsoft's own list is not a DNSBL, so SNDS remains the place to check Outlook.com status.

For JMRP complaints, the account-wide suppression list is the right target. The REST API accepts up to 1,000 addresses per call and, by default, unsubscribes them from every list; the MCP server offers the same as the suppress_emails tool (API documentation, MCP documentation).

curl -X POST https://mail.example.com/api/v1/suppressions \
  -H "Authorization: Bearer ns_live_xxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"emails": ["complainer@hotmail.com"], "reason": "jmrp_complaint"}'

Broadcasts and autoresponders sent to a list carry a one-click List-Unsubscribe header (RFC 8058), which both lowers complaints and, as shown above, lets you trace a JMRP report back to a subscriber. If you want to automate the whole loop, a mailbox that receives JMRP reports can feed an n8n workflow that calls the suppression endpoint.

🎯 Expert tips

1
Register SNDS before you need it

Access goes through PTR and RDAP contacts, which can take days to sort out with a hosting provider. Do it on the day you get the IP, not on the day of the first S3150.

2
Keep transactional mail on a separate IP

Password resets and invoices should not share an IP with newsletters. If marketing gets listed, receipts still arrive.

3
Watch the Outlook share of your list

Hotmail and Outlook.com addresses are often a large part of consumer lists. Segment them and send to them last in a campaign, so a sudden throttle shows up before the whole send is affected.

4
Treat 4.7.650 as an early warning

Temporary throttling based on reputation often comes before a hard block. Lower the volume to Microsoft domains and review complaints the same day.

5
Always reply to the automated answer

Sender support's first response is generated by a script. A short, factual reply with the requested details is what gets a person to look at the IP.

Frequently asked questions

What does error S3150 mean?

S3150 means Outlook.com has put your sending IP on its internal block list for the consumer service (@outlook.com, @hotmail.com, @live.com, @msn.com). Every message from that IP is refused with a permanent 550 5.7.1 error until the listing expires or Microsoft removes it.

How long does an Outlook S3150 block last?

Microsoft publishes no duration. Hetzner's documentation reports that S3150 limits usually lift after a few days without sending to Outlook.com, while S3140 blocks do not expire on their own and need a mitigation request.

Why does the delist portal say my IP is not blocked?

The portal at sender.office.com only covers the Microsoft 365 block list (errors 5.7.606). S3150 and S3140 come from the separate Outlook.com consumer list, which you handle through the sender support form at olcsupport.office.com.

Do I need a dedicated IP for JMRP?

JMRP sends complaints to the owner of the sending IP, so it is meant for dedicated IPs. On a shared IP pool the complaints go to the pool operator, such as your sending provider, not to you.

Does SNDS show data for small senders?

Only partly. Traffic and spam data may be missing for IPs that sent fewer than 100 messages on a given day, but the View IP Status page still shows whether the IP is blocked.

Is 550 5.7.515 the same as an S3150 block?

No. 5.7.515 means a domain sending more than 5,000 messages a day to Outlook.com failed SPF, DKIM or DMARC. It is fixed in DNS and your sending setup; no delisting request applies.

Sources

Send from IPs you control and can register in SNDS

NetSendo runs on your own server and can send through your SMTP provider or from your own dedicated IPs with warming and DKIM per domain.

#deliverability#outlook#microsoft#ip-reputation#feedback-loop
Share