Outlook.com is rejecting email from domains without DMARC

If your domain does not have a DMARC record, some of your emails to Outlook.com users may now be rejected without notice.

Beginning November 5, 2026, Microsoft's Outlook.com, Hotmail, Live, and MSN services began rejecting some emails from domains lacking a DMARC record. This change affects not only bulk senders but also ordinary, low-volume senders, a departure from Microsoft's previously announced rules that targeted senders of over 5,000 messages daily. The rejections are not publicly announced and can be inconsistent, with some messages passing while others from the same domain bounce. The bounce message indicates a lack of SPF, DKIM, or DMARC authentication records. The proposed solution is to add a simple TXT DNS record, specifically "v=DMARC1; p=none", which satisfies Outlook.com's requirement without altering how other email providers handle mail from the domain.

Microsoft's quiet implementation of DMARC enforcement signifies a broader industry trend towards stricter email authentication as a baseline requirement, not just a best practice. While initially targeting large senders, this move, by including low-volume senders, effectively raises the barrier for all domains communicating with Microsoft's consumer email platforms. This change is particularly impactful for businesses relying on email for customer engagement, invoices, or confirmations, as undelivered messages can lead to silent communication breakdowns and missed opportunities without immediate user awareness. The requirement for a DMARC record, even at the "p=none" setting, is becoming the minimum standard for deliverability across major email providers.

The implementation of DMARC checks, even for non-bulk senders, underscores the growing importance of email authentication in combating spoofing and phishing. Domains that fail to adopt DMARC, starting with the "p=none" policy, risk being increasingly sidelined by major mailbox providers. This situation necessitates that organizations, regardless of their sending volume, proactively manage their DNS records to ensure continued email deliverability. The "p=none" policy, while a minimal step, serves as an entry point for improving sender reputation and can be progressively hardened to "p=quarantine" or "p=reject" as senders become more confident in their SPF and DKIM alignment.