Outlook Is Rejecting Mail Without DMARC: What to Check
Since around 5 November 2026, email administrators have reported Outlook rejecting emails from domains that have no DMARC record, with a permanent bounce that reads "550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records". The reports cover Microsoft's consumer mailboxes (outlook.com, hotmail.com, live.com and msn.com), and they include small senders well below Microsoft's published bulk-sender threshold. As of 8 November 2026, Microsoft has not announced a policy change or explained the bounces.
For a small B2B team, this matters for a practical reason. A meaningful share of prospects, freelancers, sole traders and decision-makers still use a Hotmail or Outlook.com address, and a 5xx bounce means the message is not retried. Below, we separate what has been confirmed from what has not, then walk through a diagnosis and fix that holds up whatever Microsoft decides next.
What changed on 5 November, and what is still unconfirmed
The first public reports came from people who run mail servers. MailRoute, an email security vendor, says it first saw the bounce in its own outbound logs on 5 November 2026 (MailRoute). Al Iverson at Spam Resource reported that, by the evening of 6 November (US time), several administrators on the Mailop mailing list were seeing the same rejection (Spam Resource). Discussion then spread to Hacker News, Reddit's r/sysadmin and several Microsoft Q&A threads.
Because so much of the coverage repeats the same few sources, it helps to be precise about the strength of each claim.
| Claim | Status as of 8 Nov 2026 | Source |
|---|---|---|
| Bounce text is "550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records", sometimes followed by a code in brackets | Reported by several administrators | MailRoute, Spam Resource, Hacker News |
| Rejections began around 5 November 2026 | Reported, consistent across sources | MailRoute, mxio |
| Affected recipients are Microsoft consumer domains (outlook.com, hotmail.com, live.com, msn.com) | Reported; one test saw a Microsoft 365 business domain accept the same mail | Spam Resource |
| Mail can be rejected even when SPF and DKIM pass, if the domain has no DMARC record | Reported by administrators | Spam Resource |
Adding a DMARC record, even at p=none, fixes it |
Widely recommended; not independently confirmed for every case | MailRoute, mxio |
| Some senders with SPF, DKIM and DMARC in place still bounced | Reported, with few details | WindowsForum citing Neowin |
| Microsoft announced a new requirement for all senders | Not confirmed. No announcement found | All sources |
| The change is permanent | Unknown | n/a |
Spam Resource's test is the most useful single data point. Iverson removed the DMARC record from domains that send small volumes, and mail to an outlook.com address was rejected while mail to a Microsoft 365-hosted business domain was accepted. He also notes that other reports describe the problem as sporadic, so not every message from an affected domain bounces.
There is a dissenting view worth taking seriously. Suped, a DMARC tooling company, argued on 6 November that the reports describe individual authentication-related rejections and do not establish a new rollout or universal low-volume requirement (Suped). It also points out that a p=none policy does not guarantee acceptance by Outlook.com. That caution is correct: a generic 5.7.1 code tells you the message was refused for an authentication reason, not which check failed.
How this differs from the May 2025 bulk-sender rule
Microsoft did announce a rule in 2025, and it is easy to confuse the two. On 2 April 2025, Microsoft said that domains sending more than 5,000 emails per day to its consumer services must pass SPF and DKIM and publish DMARC at least at p=none, aligned with SPF or DKIM (Microsoft Tech Community). Non-compliant bulk mail was first routed to Junk from May 2025, with rejection to follow. That rule has its own documented error: "550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level".
The November bounces use a different code and hit senders far below 5,000 messages a day. Microsoft's 2025 post said that "all senders benefit from these best practices", but it did not extend the requirement to low-volume senders. Google's guidelines follow the same pattern: every sender needs SPF or DKIM, while DMARC is required only for senders of more than 5,000 messages a day to Gmail, and p=none is acceptable (Google Workspace Admin Help). Whatever is happening at Outlook.com, a DMARC record has been the sensible baseline for some time.
Step 1: Read the bounce before changing DNS
The fastest way to waste an afternoon is to edit DNS records based on a guess. Start with the non-delivery report (NDR) your mail server or mailbox sent back. Open the full bounce, not just the summary line, and look for the "diagnostic information for administrators" section or the raw SMTP response.
Record these details for each failure:
- The exact SMTP code and text, including any bracketed code after it
- The timestamp, with the time zone
- The recipient's domain (outlook.com, hotmail.com, live.com, msn.com, or a business domain)
- The sending system: your mailbox provider, your CRM, your outreach tool, or a website form
- The domain in the visible "From" address
Then match the code against the patterns currently in circulation.
| Bounce code and text | What it usually points to | First check |
|---|---|---|
| 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records | The November pattern. Most reports involve a From domain with no DMARC record | Does _dmarc.yourdomain.com exist? |
| 550 5.7.515 Access denied, sending domain does not meet the required authentication level | Microsoft's documented bulk-sender rule from 2025 | SPF pass, DKIM pass, DMARC published and aligned |
| 550 5.7.23 | An SPF problem, according to Microsoft's Exchange Online documentation (Microsoft Learn) | Is the sending IP or service authorised in SPF? |
If the bounce came from a business domain hosted on Microsoft 365 rather than a consumer address, the November reports may not apply at all. Treat that as a separate investigation into the recipient's own filtering rules.
Grouping failures this way also tells you how big the problem is. If only one tool, such as a CRM that sends on your behalf, produces bounces, the issue is likely that tool's SPF or DKIM setup, not your domain as a whole.
Step 2: Check SPF, DKIM, DMARC and alignment
DMARC does not authenticate anything on its own. It tells receivers to check that SPF or DKIM passed for a domain that matches the visible From address, and what to do if neither did. That is why all three records need to be checked together.
The commands below work on macOS and Linux. Replace example.com with your From domain and selector with your DKIM selector.
# SPF: should return exactly one record starting with v=spf1
dig +short TXT example.com
# DMARC: should return one record starting with v=DMARC1
dig +short TXT _dmarc.example.com
# DKIM: the selector depends on your mail provider
dig +short TXT selector._domainkey.example.com
Free web-based lookup tools do the same job if your team prefers not to use a terminal.
SPF
SPF lists the servers allowed to send mail for a domain. The record lives on the domain used in the envelope sender (the return path), which is not always the same as the visible From address. Common problems on small business domains:
- Two SPF records. A domain can have only one TXT record that starts with
v=spf1. A second one, often added when a new tool is connected, makes SPF fail with a permanent error. - Missing senders. Every service that sends as your domain needs to be covered, including your mailbox provider, newsletter tool, CRM, help desk and website form plugin.
- Too many lookups. Each
include,a,mx,ptrandredirectmechanism triggers a DNS lookup, and SPF evaluation fails after ten (RFC 7208). Long chains of includes from many tools reach that limit faster than most teams expect.
DKIM
DKIM adds a cryptographic signature that receivers verify against a public key in your DNS. Your mail provider tells you which selector and record to publish, and most providers have a setting that must be switched on before outgoing mail is signed. The key point for DMARC is the signing domain: if a third-party tool signs with its own domain rather than yours, DKIM passes but does not align.
Alignment
Alignment is the part most teams miss. DMARC passes only if SPF or DKIM passes for a domain that matches the From domain, either exactly or as a subdomain under the default "relaxed" mode. A message from sales@example.com, sent through a tool that uses its own return path and signs with its own domain, can pass SPF and DKIM and still fail DMARC.
To check alignment on a real message, send a test to a mailbox you control, open the full headers and find the Authentication-Results line. Look for dmarc=pass and note which domain is shown next to spf=pass and dkim=pass. If neither matches your From domain, fix the tool's custom domain or DKIM settings before going further.
Step 3: Publish a minimal DMARC record and retest
If your domain has no DMARC record, publishing one is the change with the strongest evidence behind it. Every source we reviewed recommends it, and Microsoft's own 2025 rule names p=none as the minimum. Create a TXT record at _dmarc on your From domain:
Host: _dmarc
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
Each part has a job:
v=DMARC1identifies the record and must come first.p=nonetells receivers to take no special action on failures. It publishes a policy without putting legitimate mail at risk while you check alignment.rua=mailto:...asks receivers to send aggregate reports. These daily XML summaries show which servers send as your domain and whether they pass. A shared mailbox or a free report-parsing service makes them readable.
A few cautions apply. Publish only one DMARC record per domain, because two records are treated as no valid record. If your domain already has DMARC, leave it in place and investigate SPF, DKIM and alignment instead. Do not jump straight to p=quarantine or p=reject to fix a bounce: an enforcing policy only helps once every legitimate sender passes, and moving too early can stop invoices, password resets or replies from arriving.
Retest and confirm
DNS changes can take time to propagate, depending on the record's TTL. Once the record resolves, retest in this order:
- Confirm the record from outside your network with
digor a web lookup. - Send a plain test message from each sending system to an outlook.com or hotmail.com address you control.
- Check the received headers for
dmarc=passand check that the message reached the inbox or junk folder rather than bouncing. - Resend any genuinely important messages that bounced. Outreach sequences may need the affected contacts re-queued manually, because a hard bounce often marks a contact as undeliverable.
On that last point, check your tools' suppression lists. Many email platforms automatically suppress an address after a hard bounce, which is the right behaviour for invalid mailboxes but wrong for valid prospects bounced by an authentication problem. Remove those addresses from suppression only after the retest succeeds.
Step 4: When your records are correct and mail still bounces
Some administrators report that domains with SPF, DKIM and DMARC already in place were still rejected, and one case summarised by WindowsForum involved a message that was rejected and then delivered roughly 19 minutes later (WindowsForum). Neither Microsoft nor any of the sources we reviewed has explained those cases. If your records check out, we recommend treating the rest as an evidence-gathering exercise rather than continuing to change DNS.
Keep a simple incident log:
- Copies of the full bounces, with timestamps and recipient domains
- The DNS records as they stood when the bounces happened, and when each change was made
- The header results from successful test messages after each change
- The sending IP addresses, which appear in the bounce or your provider's logs
This record serves two purposes. It lets you show your mailbox provider, outreach vendor or IT contractor exactly what happened, and it gives you a clean before-and-after if Microsoft later confirms or reverses a change. Microsoft's postmaster site for Outlook.com (Microsoft Postmaster) is the route for raising a delivery problem with consumer Outlook mailboxes and for its Smart Network Data Services (SNDS) programme, which gives IP owners visibility of how their traffic is treated. If you send through a shared provider such as a hosted mailbox, ask that provider to raise it, because the sending IPs are theirs.
It also helps to keep the business impact in proportion. An authentication bounce is a delivery problem, not a reputation verdict. We found no published evidence either way on whether a short spell of these bounces affects later delivery, so the priority is simply to correct the records and keep the evidence.
What this means for small B2B outreach
Small teams rarely set up email authentication deliberately. The domain was registered years ago, a mailbox provider added SPF, someone connected a CRM, and DMARC never came up because Gmail did not require it at low volume. This week's bounces are a reminder that the defaults which worked yesterday are not guaranteed tomorrow.
Three points are worth taking into planning:
- Authentication belongs to the domain owner. Whatever tool sends the message, receivers judge the From domain. That is also how Meirra Email is built: cold outreach is sent through the customer's own SMTP account, so the authentication that counts is the customer's own SPF, DKIM and DMARC, and one customer's setup cannot affect another's.
- Bounce data is a diagnostic signal. A sudden cluster of 5.7.x bounces on one recipient domain is an authentication or policy event, not a list-quality problem. Checking bounce codes by recipient domain each week catches this kind of change early.
- List quality and authentication are separate problems. Verifying addresses before sending reduces invalid-mailbox bounces; it does nothing for an authentication rejection. Teams building lists with a tool such as Meirra Leads still need their sending domain set up correctly.
If your team would rather have specialists audit the setup across every tool that sends as your domain, our email marketing services cover that work.
Key takeaways
- Confirmed: since around 5 November 2026, Outlook.com, Hotmail, Live and MSN addresses have rejected some mail with "550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records", mostly from domains without a DMARC record and including low-volume senders.
- Not confirmed: the cause, the scope and whether it is permanent. As of 8 November 2026, Microsoft has made no announcement, and some senders with valid records also report bounces.
- Diagnose first: read the full bounce, group failures by code, recipient domain and sending tool, then check SPF, DKIM and DMARC alignment on the From domain.
- Minimum fix: publish one DMARC record at
_dmarcwithp=noneand anruaaddress, make sure SPF or DKIM passes in alignment, retest to an Outlook.com address, then clear wrongly suppressed contacts. - Keep evidence: log bounces, DNS changes and test results, so you can escalate with facts and compare outcomes if Microsoft clarifies its position.
A DMARC record with an aligned SPF or DKIM pass was already the baseline at Google and for Microsoft's bulk senders. Whatever the explanation for this week's bounces turns out to be, setting it up now is a small, durable fix that leaves your domain better prepared for the next change.
Where does your own site stand?
Run a free audit: enter your domain and get a dated, sourced record of what is publicly visible about your site. No login, no card. Prefer to talk it through? Book a consultation with our team.