Story

Outlook Is Rejecting Email Without DMARC: What Indie SaaS Founders Should Check

Outlook rejecting email without DMARC is what mail operators started reporting on 5 November 2026. Thomas A. Johnson, founder and CEO of MailRoute, an email relay vendor, wrote on 6 November that Outlook.com, Hotmail, Live, and MSN were turning away some mail from domains with no DMARC record.

He wrote that the rejection hits low-volume senders, and that only part of the messages bounce. The domains he had seen mostly had working SPF. Many of them had DKIM. His line on the silence: “Nobody announced it. The fix is one DNS record.”

This story is dated 9 November 2026 in Sydney. Sydney is on Australian Eastern Daylight Time, eleven hours ahead of UTC. Dates below follow the source. The posts checked here are operator reports. As of 6 November, Johnson wrote that Microsoft had published nothing.

For a small SaaS, the mail is specific. A sign-up confirmation. A receipt. A password reset. A support reply. A cold note to someone on outlook.com, hotmail.com, live.com, or msn.com. When that copy is one of the ones being rejected, the person never sees it. The signal on the sender’s side is the bounce.

What Outlook rejecting email without DMARC looks like

The bounce Johnson published is 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519). He wrote that the first day of reports left off the bracket code.

Spam Resource, in a post dated 6 November 2026 in US time and titled “Microsoft newly rejecting mail lacking DMARC?”, says multiple email admins on the Mailop mailing list reported the same kind of rejection. They were sending to Outlook consumer addresses. The sending domain had no DMARC record. SPF and DKIM still passed. In the author’s own test, mail to a Microsoft 365-hosted corporate domain was accepted.

DmarcDkim.com, a DMARC-report vendor, says operators on Mailop, Fastmail, and MailRoute reported the bounce. Read that page as vendor guidance. It describes a researcher test on 7 November: DMARC was deleted from low-volume domains, Outlook.com returned the 550 5.7.1 rejection, and a Microsoft 365 company domain accepted the mail. Rejections are partial. One admin saw about half of clients bounce.

Why is Outlook.com rejecting my email?

Microsoft already publishes a bulk rule, and it uses a different code. Microsoft Support says that since May 2025, domains sending more than 5,000 messages a day to Outlook.com consumer domains must pass SPF, DKIM, and DMARC, or they get 550 5.7.515 Access denied.

The bounce in this week’s reports is 550 5.7.1. MailRoute says it hits low-volume senders. A poster on the Hacker News thread below is the other source for the 5.7.1 rejection reaching small senders. The May 2025 page is a volume rule. The reports this week describe a missing-DMARC rejection under that volume.

The Hacker News thread “Microsoft requiring DMARC now or just us?” was posted on 7 November 2026 and points at the Mailop thread. One commenter said it started on 5 November for them. Another said it began on 6 November and increased on 7 and 8 November. One welcomed it: “About time.” One said an email host, mxroute.com, notified customers. A commenter noted a DMARC fix of p=none. The thread also links a Mastodon discussion started by Mythic Beasts.

The welcome belongs in the record. So does the limit on what the record is. Johnson wrote that, as of 6 November, Microsoft had published no postmaster notice, no blog post, and no service-health entry. The rejections in these reports are partial. They are reports, and Microsoft has not confirmed them in the sources above.

A short timeline

  • 5 November 2026. First reports. MailRoute says Outlook.com, Hotmail, Live, and MSN have been turning away some mail from domains without DMARC since this day. A commenter on the Hacker News thread said it started that day for them. Johnson says the first day’s bounce did not include the bracket code.
  • 6 November 2026. Johnson publishes the MailRoute post: nothing from Microsoft, low-volume senders hit, only part of the messages bounced. Spam Resource, dated that day in US time, writes up Mailop reports of rejections to Outlook consumer addresses when the domain has no DMARC record, even with SPF and DKIM passing.
  • 7 November 2026. The Hacker News thread is posted. DmarcDkim.com describes a researcher test the same day: deleting DMARC on low-volume domains drew the 550 5.7.1 from Outlook.com, while a Microsoft 365 company domain accepted the mail.
  • 8 November 2026. The Hacker News commenter who said the rejections began on 6 November also said they increased on 7 and 8 November.

How do I fix 550 5.7.1 Message lacks SPF/DKIM/DMARC Auth Records?

Johnson’s fix is one TXT record. The host is _dmarc. The value is v=DMARC1; p=none. He writes that this changes nothing about how other receivers treat the mail. DMARC passes only if SPF or DKIM aligns with the From domain.

Four checks, taken from those reports.

1. Look the record up. Use your domain in place of example.com. MailRoute says no output means there is no record.

dig +short TXT _dmarc.example.com

2. Publish one TXT record at _dmarc if that lookup is empty.

v=DMARC1; p=none

3. Check alignment, and keep a single record. DMARC passes only if SPF or DKIM aligns with the From domain. Postmark’s support note says strict SPF alignment, aspf=s, does not work with Postmark, because the return-path is a subdomain. Relaxed alignment is the default. DmarcDkim.com says to keep one record. Two DMARC records are ignored.

4. Resend anything that already bounced. A 550 is permanent, so the rejected copy does not go out again on its own. The same vendor page says a few admins still see the error with DMARC present, and that those cases go to Microsoft sender support.

A Microsoft Q&A thread has an admin report that Hotmail accepted mail once the DMARC record showed up. The same thread says Microsoft 365 never creates a DMARC record for you.

Do small senders and indie SaaS need DMARC now?

Spam Resource’s advice, in that 6 November post, is that if you send email from a domain, you need a DMARC record in place, even if you are not a bulk sender. That advice sits next to the author’s test, in which a Microsoft 365 corporate domain still accepted the mail.

The May 2025 rule on Microsoft’s support page is the bulk line: more than 5,000 messages a day to Outlook.com consumer domains. The reports this week describe a 550 5.7.1 that reaches senders under that line. Johnson says low-volume senders were among the domains he saw. The Hacker News poster says this bounce reaches small senders. Those sentences are theirs. They are not Microsoft stating a new threshold.

A small product still sends mail that has to arrive. Launch mail. The note that finishes onboarding. A newsletter someone asked for. A password reset for a customer who signed up with a personal Microsoft address. Building and selling a product you own includes the message that lets someone finish creating an account. If Outlook.com rejects that copy, the person never gets the link.

A platform can change a channel you do not control. Reddit’s login wall is a recent case: a site people use to be found changed the terms. This week’s reports are the mailbox at the end of a signup.

Consumer Microsoft addresses and a company domain on Microsoft 365 are different deliveries in the tests that were published. Spam Resource’s test, and the researcher test DmarcDkim.com describes, both had the corporate Microsoft 365 domain accept mail that Outlook.com rejected.

Will adding DMARC p=none hurt my deliverability or change how Gmail treats my mail?

Johnson says the value v=DMARC1; p=none changes nothing about how other receivers treat the mail. That is the claim these reports support. The same sources do not describe a separate Gmail penalty, or a Gmail reward, for publishing p=none.

Resend’s DMARC doc lists the policies as none, quarantine, and reject, and it says to start with monitoring. p=none is that monitoring policy, and it is the value MailRoute published as the fix. Quarantine and reject are the other rows on that table.

Publishing the record leaves a message that already took a 550 where it is. Those need a resend. Because only part of the messages bounce, one test that arrives does not show that the rest will. Johnson says only part of the messages bounce. DmarcDkim.com says one admin saw about half of clients bounce.

Is Microsoft 365 or a transactional email provider enough on its own?

The reports say you still add the record yourself. The Microsoft Q&A thread says Microsoft 365 never creates a DMARC record for you. DmarcDkim.com says Microsoft 365 needs DKIM enabled for the custom domain, via the selector1 and selector2 CNAME records. A tenant that can send still leaves that DNS unpublished until you add it.

A transactional provider leaves the same gap. Resend’s docs say that verifying a domain sets up SPF and DKIM. DMARC is not set up for you. Postmark’s note is the alignment caveat: strict SPF alignment does not fit a return-path on a subdomain, and relaxed alignment is the default.

That DNS step sits with you, in the same way a key sits with the provider that issued it. Rotating API keys after the Trigger.dev and GitBook breaches is the chore of doing the revocation at the source. Verifying the domain inside Resend, or sending through Microsoft 365, does not publish DMARC.

If the record is already present and the 550 continues, DmarcDkim.com says a few admins are in that spot, and the next step they name is Microsoft sender support. That is vendor guidance. It leaves the one-line TXT record as the fix the operators published, and it leaves a remainder that the record alone has not cleared for everyone who tried it.

Have you seen Outlook bounces on a domain that already had SPF and DKIM, and should a small sender have to publish DMARC?

FAQ

Why is Outlook.com rejecting my email?

Since 5 November 2026, mail operators have reported that Outlook.com, Hotmail, Live, and MSN turn away some mail from domains with no DMARC record. Thomas A. Johnson, founder and CEO of MailRoute, wrote on 6 November 2026 that the bounce is 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519), that the first day of reports omitted the bracket code, and that it hits low-volume senders. He wrote that only part of the messages bounce, and that the domains he had seen mostly had working SPF, with many also having DKIM. Spam Resource, the same day in US time, said Mailop admins saw rejections to Outlook consumer addresses even when SPF and DKIM pass, while a Microsoft 365 corporate domain accepted mail in the author's test. As of 6 November, Johnson wrote that Microsoft had published no postmaster notice, blog, or service-health entry. This is separate from Microsoft's May 2025 bulk rule, which uses 550 5.7.515 for domains sending more than 5,000 messages a day. Microsoft has not confirmed the newer bounce in the sources checked here.

How do I fix 550 5.7.1 Message lacks SPF/DKIM/DMARC Auth Records?

MailRoute's fix is one TXT record at _dmarc with the value v=DMARC1; p=none. Check with dig +short TXT _dmarc.example.com, using your domain in place of example.com. No output means there is no record. DMARC passes only if SPF or DKIM aligns with the From domain. Keep a single DMARC record, because DmarcDkim.com says two records are ignored. A 550 is permanent, so mail that already bounced has to be sent again. An admin on a Microsoft Q&A thread said Hotmail accepted mail once the DMARC record showed up. DmarcDkim.com, a DMARC-report vendor, says a few admins still see the error with DMARC present and points those cases to Microsoft sender support.

Do small senders and indie SaaS need DMARC now?

Spam Resource's 6 November 2026 advice is that if you send email from a domain, you need a DMARC record in place, even if you are not a bulk sender. MailRoute says the new rejection hits low-volume senders, and a Hacker News poster is the other source for it reaching small senders. Microsoft's published May 2025 rule is the bulk line: more than 5,000 messages a day to Outlook.com consumer domains, or 550 5.7.515. The 550 5.7.1 reports are a different bounce. For an indie SaaS that mail is the sign-up confirmation, the receipt, the password reset, the support reply, and cold outreach to a personal Microsoft address. The reports describe a partial rejection, and Microsoft had not announced it as of 6 November.

Will adding DMARC p=none hurt my deliverability or change how Gmail treats my mail?

MailRoute says the TXT value v=DMARC1; p=none changes nothing about how other receivers treat the mail. The sources checked for this story do not describe a separate Gmail penalty or reward for p=none. Resend's DMARC doc lists policies of none, quarantine, and reject, and says to start with monitoring. p=none is the monitoring value MailRoute published as the fix. It does not retry a message that already received a 550, and only part of messages are bouncing, so one successful test does not show that every copy will land.

Is Microsoft 365 or a transactional email provider enough on its own?

On the reports here, no. A Microsoft Q&A thread says Microsoft 365 never creates a DMARC record for you. DmarcDkim.com says Microsoft 365 needs DKIM enabled for the custom domain, using the selector1 and selector2 CNAME records. Resend's docs say SPF and DKIM are set up when you verify a domain, and that DMARC is not automatically set up. Postmark says strict SPF alignment, aspf=s, does not work with Postmark because the return-path is a subdomain, and that relaxed alignment is the default. A few admins still report the 550 with DMARC present. DmarcDkim.com, a DMARC-report vendor, says those cases go to Microsoft sender support.