Live · updated just now

Microsoft is wrongly blocking genuine business emails to Outlook and Hotmail users

Tuesday, 10 November 2026 · Marketing & design · Full report

What was found

Beginning November 5, Microsoft's consumer email services (Outlook, Hotmail, Live and MSN addresses) started turning away some genuine business messages 1. The rejected mail mostly came from senders that had not set up the standard sender-verification tools known as DMARC, SPF or DKIM. Senders received bounce messages with the codes 550 5.7.1 and 550 5.7.23 1. Since May 2025, Microsoft has required DMARC only from bulk senders who send more than 5,000 messages a day. These new failures, however, hit small senders too, and even some domains that had verification set up correctly 1. Microsoft gave no public warning and posted no service alert about the change 1.

Who it applies to

The problem matters most for small and everyday senders. That includes small and medium businesses, schools, charities and nonprofits, and professional offices such as law or accounting firms. It also affects larger organizations' secondary or less-used domains. On the receiving side, anyone with a Microsoft consumer mailbox may be missing messages they expected 1.

How strong the evidence is

Early. This is a news report and incident analysis based on several user reports. It does not give a count of how many sending domains or messages were affected 1. It is still unclear whether Microsoft quietly changed its policy or whether a software fault is causing the rejections. The failures also come and go, so the same sender may succeed one day and fail the next. Microsoft has issued no formal notice, service health entry or statement explaining what is happening 1. The full article was read, but its text was cut off near the end, so some details may be missing.

What it means in practice

Organizations that send email to Outlook, Hotmail, Live or MSN addresses should check whether their domain has a DMARC record. They can do this with a simple DNS lookup. If no record exists, they can add a basic one, such as a TXT record set to "p=none." This lets the domain declare a policy without blocking any of its own mail 1. They should also make sure SPF and DKIM are configured, because the three tools work together to prove that mail really comes from the stated sender 1. Taking these steps lowers the chance of rejection, though some properly set-up domains were still affected. Watching for 550 bounce codes can help organizations spot problems early.