Blog

Outlook.com Is Bouncing Small Business Email Without DMARC: The 5-Minute Fix

If a customer with a Hotmail or Outlook.com address told you this week that your invoice, quote, or contact-form reply never showed up, it may not be their spam folder. Since Thursday, November 5, 2026, Microsoft’s consumer email service has been rejecting some messages from ordinary small business domains that do not have a DMARC record — even when those domains already have SPF and DKIM set up correctly.

Microsoft has not announced this. There is no blog post, no postmaster notice, and no service-health entry. But email administrators around the world have reproduced it, and the fix is a single DNS record that takes about five minutes to add. Here is what is happening, who it affects, and what I would do today if your business sends email from its own domain.

What Changed at Outlook.com

Abstract illustration of an email envelope bouncing back from a mail server shield while a second envelope with a green check passes through

The bounce message looks like this: 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519). According to MailRoute’s write-up, first published November 6, the servers behind outlook.com, hotmail.com, live.com, and msn.com addresses started returning this rejection on November 5. The common factor in the rejected mail MailRoute examined was a missing DMARC record, including domains whose SPF and DKIM were already in place.

Email deliverability expert Al Iverson confirmed it himself. In his November 7 Spam Resource post, he deleted the DMARC record from a handful of his own non-bulk domains and sent test mail. Mail to an outlook.com address was rejected. Mail to a company domain hosted on Microsoft 365 was accepted. In other words, this hits mail going to Microsoft’s free consumer mailboxes, not mail going to businesses that use Microsoft 365.

Two details matter for small businesses:

  • Volume does not matter. Microsoft’s published rule, in force since May 2025, only covers domains sending more than 5,000 messages a day, and it uses a different error code (550 5.7.515). This new rejection reaches small domains too, per MailRoute.
  • It is sporadic. Not every message bounces. One email gets through, the next one is rejected. So “it worked yesterday” does not mean your domain is fine.

It is also a permanent rejection. As Engagor’s November 8 analysis points out, a 550 is not a soft bounce that gets retried later. If your message got this response, your customer never received it, and it will not arrive unless someone sends it again.

Why This Hits Small Businesses Hardest

Abstract illustration of three DNS record cards where two are complete with green checks and the third slot is empty with a warning

Here in Miami, I see the same setup over and over. A business buys a domain, sets up email through Microsoft 365 or Google Workspace, connects a website contact form, maybe an invoicing tool or a booking app. SPF gets added during setup. DKIM sometimes gets turned on. DMARC almost never gets added, because nothing forces you to — until now.

Engagor makes a point that every Microsoft 365 customer should hear: Microsoft 365 walks you through SPF and lets you enable DKIM, but it never publishes a DMARC record for your custom domain. Many small businesses have run for years with SPF and DKIM and no DMARC. And the error message makes it worse. When a Microsoft 365 user sends to a Hotmail address and gets bounced, the notice can start with “550 5.7.23 … Sender Policy Framework violation,” so people spend an afternoon checking SPF, which was fine all along. The real reason is in the second half of the line.

Another trap: you may think you already have DMARC because an email header said dmarc=pass. Engagor notes that Microsoft 365 can record a “best guess” pass when no DMARC record exists at all. Do not trust a header. Check DNS.

Think about what flows through your domain: quotes, invoices, appointment confirmations, password resets from your online store, and replies to website inquiries. Plenty of your customers still use Hotmail and Outlook.com addresses. A silent bounce on a quote is a lost job you never hear about.

The Five-Minute Fix: Add a DMARC Record

Abstract checklist cards for checking DNS, adding a DMARC record, and resending bounced email

Every source I read agrees on the fix, and in every confirmed case it has worked. Here is the checklist I am running for clients this week:

  1. Check whether you have DMARC. Look up the TXT record at _dmarc.yourdomain.com with a free DNS checker, or run nslookup -type=TXT _dmarc.yourdomain.com. If you see a record starting with v=DMARC1, you have one. If you get nothing, you do not.
  2. Add one record if it is missing. Wherever your DNS is hosted (often your registrar, Cloudflare, or your host), add a TXT record with the name _dmarc and the value v=DMARC1; p=none. MailRoute warns that many DNS panels add your domain automatically, so typing the full _dmarc.yourdomain.com can create a broken record.
  3. Publish exactly one. Two DMARC records on the same domain is itself an error. If you already have one, keep it. If you are already at p=quarantine or p=reject, do not weaken it — the record is not your problem.
  4. Make sure SPF or DKIM actually passes for every service that sends as your domain: your mailbox provider, your website’s contact form, your CRM, your newsletter tool. A DMARC record with neither passing still fails.
  5. Resend anything that bounced. Search your inbox for “lacks SPF/DKIM/DMARC” or “AS9031519” since November 5 and send those messages again once the record is live. Engagor reports the record took effect anywhere from a few minutes to about 90 minutes, depending on DNS caching.

A p=none policy does not change how your mail is handled anywhere else. It just tells receivers that your domain uses DMARC. Later, you can add a reporting address (rua=) to see every service sending as your domain, then tighten the policy once everything legitimate passes. mxio’s updated sender-requirements guide lays out that progression from p=none to quarantine to reject.

Is This Permanent?

Nobody outside Microsoft knows yet. As of November 8, Engagor reported that Microsoft had said nothing publicly, and Iverson wrote that he is not sure whether this is an intended policy update. But his advice is the same as mine: add the record anyway. Gmail and Yahoo already require DMARC for bulk senders, and the direction is clear. Even if Microsoft rolls this back tomorrow, a DMARC record is something your domain should have had already, and it also makes it harder for scammers to send email pretending to be you.

If you do not run your own mail server and none of this makes sense, that is fine. Contact whoever sends your email — your email provider, CRM, or marketing platform — or your web designer. This is a change on the sender’s side. Your customer with the Hotmail address cannot fix it for you.

Want Us to Check Your Domain?

Most of the time this is a quick fix, but it is easy to get wrong in a DNS panel. Contact Final Web Design and we will check your domain’s SPF, DKIM, and DMARC records, make sure your website contact forms and other tools are sending properly, add the DMARC record if it is missing, and set up reporting so the next surprise change from a mailbox provider is a non-event instead of a week of lost leads.

Sources: MailRoute, “550 5.7.1 Message lacks SPF/DKIM/DMARC Auth Records (Outlook.com)” (Nov 6, 2026); Al Iverson, Spam Resource, “Microsoft newly rejecting mail lacking DMARC?” (Nov 7, 2026); Engagor, “Microsoft’s AS9031519: Outlook.com Now Rejects Mail From Domains Without a DMARC Record” (Nov 8, 2026); mxio, “Google, Yahoo, and Microsoft Bulk Sender Requirements (2026)” (Nov 6, 2026).

Related Articles