Outlook.com rejects mail from small senders without DMARC

Until now, a missing DMARC entry was usually tolerated by large mailbox providers, particularly when SPF and DKIM were in order. Microsoft's consumer service now appears to treat the absence of DMARC as a reason to refuse delivery from smaller senders. For affected senders, the practical effect is bounced messages despite a technically correct setup.

Who is affected and what to do

The problem hits small organisations, clubs, shops and self-hosted mail operators most, since they often run their own domains without having added a DMARC policy. Messages to Outlook.com addresses may fail silently from the sender's point of view, which makes the issue easy to overlook until recipients complain.

The straightforward remedy is to publish a DMARC record in the domain's DNS. Even a basic policy, which only monitors traffic and does not yet instruct receivers to block anything, gives the domain the entry that the provider now expects. Administrators should also check bounce messages for rejection notices from Microsoft and confirm that SPF and DKIM are aligned with the domain used in the From address.

The episode shows how requirements for mail authentication keep tightening. Operators who have so far relied on SPF and DKIM alone should treat DMARC as a baseline rather than an optional extra.