Microsoft’s Outlook.com service faced widespread email delivery issues last week, with some messages being blocked or rejected, causing frustration for users. A source familiar with the problem described the situation as “carnage.”
The disruption appears linked to certain IP addresses being flagged by Microsoft’s systems—either due to reputation rules or automatic inclusion on block lists.
One reader shared their experience: “At the end of January, we noticed a sudden surge in rejections for customers with static IPs, but only when sending to free Outlook accounts.”
Affected senders received a 550 error, instructing them to contact their Internet Service Provider because “part of their network is on our block list.”
Block lists play a key role in preventing spam, filtering messages from addresses or networks associated with junk email. Yet, in this case, the reader’s company showed no issues in Microsoft’s Smart Network Data Service (SNDS).
“We’re also part of their Junk Mail Reporting Program,” the reader added, “which should alert us if anyone reports spam from our IPs—but we never received any reports.”
The problem intensified in February. Discussions on Microsoft’s support forums revealed more users encountering similar email delivery failures. One post noted: “We are experiencing a critical and recurring delivery problem for recipients at outlook.com, live.com, hotmail.com, and msn.com,” citing a server error indicating temporary rate limiting due to IP reputation.
Despite the reference to “rate limiting,” the reality was that many emails simply weren’t being delivered.
Administrators from a wide range of organizations—including Estonian public libraries and healthcare email providers—confirmed experiencing the same issues, with Microsoft support offering little assistance.
The reader explained: “Customers are struggling to send invoices, order confirmations, authentication codes—messages that have always been accepted by Outlook before—only to have them blocked or rejected now.”
They also pointed out a common misconception: when users see a 550 error, they often assume their ISP is blocking the email, not realizing that the receiving server is refusing it.
“Most people don’t read or understand these notifications,” the reader noted. “They blame the ISP or the sender and move on, which can lead to lost business or confusion.”
Microsoft was contacted for comment but did not provide a detailed response beyond acknowledging the inquiry.
While filtering spam is important, the incident highlights the need for clear, fast resolution processes when legitimate emails are mistakenly blocked. Each failed delivery—whether an invoice, receipt, or notification—can damage a business’s reputation, even when the sender has done nothing wrong.
thetechtrident.com 