Lorixen.
EN

Outlook and Hotmail Rejecting Your Business Emails: S3150 and 550 5.7.1 Explained

Short answer: An S3150 code inside a 550 5.7.1 bounce means Microsoft's consumer mail service (Outlook.com, Hotmail, Live, MSN) has refused mail from the sending IP address, usually because that IP has a poor reputation or sits on Microsoft's internal block list. It is not the same as an authentication failure, although weak SPF, DKIM or DMARC makes everything worse. Read the bounce to see which IP was blocked, confirm whether that IP belongs to you or to a shared host, fix your domain records, then file a delisting request through Microsoft's sender support form. If the IP is a shared one on cheap hosting, the lasting fix is to send through a reputable mail provider instead.

Reading the bounce, one line at a time

Bounces look like noise, but each part tells you something. Here is an example of the kind of message a small firm might receive after emailing an invoice to a customer at a Hotmail address (the addresses and IP are invented):

Remote server returned: 550 5.7.1 Unfortunately, messages from [203.0.113.45]
weren't sent. Please contact your Internet service provider since part of their
network is on our block list (S3150).
  • 550 is a permanent failure. The receiving server will not accept the message if you simply send it again.
  • 5.7.1 is the enhanced status code for "delivery not authorised" or a policy refusal.
  • [203.0.113.45] is the IP address that connected to Microsoft. This is the most important detail on the page.
  • S3150 is Microsoft's own reason code for an IP or range on its block list.

Other Microsoft codes you may meet include S3140 (also an IP reputation block) and messages mentioning "access denied" or a missing reverse DNS entry. Treat any of them as a reputation problem first.

IP block or domain problem? Separate the two

Before touching DNS, work out what was actually judged. Two very different situations produce rejections from the same receiver.

Symptom Likely cause Who fixes it
Bounce names an IP and S3150 or S3140 IP or range is blocked Whoever controls that IP, plus a delist request
Bounce mentions SPF, DKIM or DMARC failing Domain authentication You, in your DNS
Mail arrives but lands in Junk Content, reputation or alignment Mostly you
Only one customer bounces Their own rules or a typo Check the address first

Look up the IP from the bounce. If it belongs to your web host's shared mail server, you are paying for the behaviour of every other account on that machine. If it belongs to a provider such as Microsoft 365 or Google Workspace, the block is rarer and usually short lived, and support for that provider should be your first call.

Check SPF, DKIM and DMARC alignment

Even when the bounce is clearly about an IP, authentication gaps make a delist request harder to win and invite the next block. Check these three records for the domain in your From address.

  1. SPF. Look up the TXT record starting with v=spf1. Every service that sends as your domain (mailbox provider, invoicing tool, website contact form) must be covered by an include or IP entry. There must be only one SPF record, and it should end in ~all or -all.
  2. DKIM. Your sending service publishes a public key, often as a CNAME or TXT record with a selector such as selector1._domainkey. Send a test to any mailbox you control, open the full headers and confirm dkim=pass for your own domain, not the provider's.
  3. DMARC. A TXT record at _dmarc.yourdomain.co.uk that starts with v=DMARC1. Starting with p=none and a reporting address is fine. What matters is that SPF or DKIM passes and lines up with the visible From domain.

Alignment is where small offices trip up. An accounting package may send with a DKIM signature for its own domain while showing yours in From. That passes DKIM but fails DMARC alignment. Most of these tools have a "custom sending domain" or "verify your domain" setting that adds the right records. Microsoft explains how it evaluates these checks in its email authentication overview.

Get the IP removed from Microsoft's list

Once the records are tidy, ask Microsoft to look again.

  1. Open the Outlook.com sender support page and choose the delist or sender support request form.
  2. Enter the blocked IP exactly as it appears in the bounce, a contact email that is not on Outlook.com or Hotmail, and the full bounce text.
  3. Confirm the email Microsoft sends you to validate the request.
  4. Read the reply carefully. It either confirms mitigation, says the IP does not qualify, or asks for more information. If it does not qualify, reply to the ticket with a short, factual explanation: what you send, to whom, how recipients opted in and what you changed.

Delisting is not instant and is never guaranteed. While you wait, avoid resending the same batch repeatedly, because repeated hits from a blocked IP do not help.

Watch the IP with SNDS

If you control a dedicated sending IP, register it with Microsoft's Smart Network Data Services. SNDS shows how much mail Microsoft saw from that IP, complaint rates and spam trap hits, using a simple colour rating. It only helps if the IP is yours alone. On a shared host you will not be able to register the IP, which is itself a sign that the address is outside your control.

A weekly glance is enough for a small business. A sudden spike in volume or a red rating usually points to a compromised mailbox or a website form being abused to send spam, so check those before anything else.

When to move sending to a dedicated provider

For a firm sending invoices and replies, the most reliable setup is mail sent by a business mailbox provider, with transactional or bulk mail sent by a specialist service. Consider moving if:

  • your mail goes out through a shared hosting server whose IP you cannot see or register
  • the same block returns within weeks of a successful delist
  • your website, CRM and invoicing tool all send directly from the web server
  • newsletters and invoices leave from the same address and IP

After the move, update SPF to include the new service, publish its DKIM records, and remove the old server from SPF so nobody else on that host can pass as you.

A quick checklist before you resend invoices

  • The bounce IP is identified and you know who owns it
  • One SPF record covers every service that sends as your domain
  • DKIM passes for your own domain on a test message
  • DMARC exists and alignment passes
  • A delist request has been filed with the full bounce text
  • Website forms and old mailboxes are checked for abuse

FAQ

Will changing my SPF record alone clear an S3150 block?

Usually not. S3150 is tied to the connecting IP, so DNS changes improve your standing but the IP still needs to be mitigated through Microsoft's form or replaced.

Why do Gmail customers receive the same invoices without trouble?

Each mailbox provider keeps its own reputation data. An IP can be fine at Google and blocked at Microsoft, which is why the bounce text from each receiver matters.

How long does a delist request take?

Microsoft does not promise a fixed time. Many requests receive an automated reply quickly, while escalations can take longer. Plan to send urgent invoices from a different, clean route meanwhile.

Can a customer whitelist us on their side?

A Hotmail user can add you to safe senders, which helps with Junk filtering, but it does not override an IP block at the server level.

If your invoices keep bouncing and you would rather have someone untangle the mail routing for you, tell us what you are seeing and we will help you get messages back into Microsoft inboxes.

Sources

WhatsAppBook a call