Users fume over Outlook.com email 'carnage'

Source: Hacker News

Background

The problem affects certain IP addresses whose emails are rejected due to falling foul of reputation rules or appearing on a block list. A Register reader reported:

“At the back end of January we noticed a sudden spike in customers’ static IPs being rejected by only Microsoft Outlook free / personal accounts.”

The returned message was a 550 error, instructing customers to contact their Internet Service Provider (ISP) because “part of their network is on our block list.”

Why the Block List Matters

A block list helps stem the flow of spam from networks or addresses associated with junk email. However, the reader’s company was not on Microsoft’s “naughty step” for email. A look at Microsoft’s Smart Network Data Service (SNDS) showed no issues with the IP.

“We’re also a member of their JMRP (Junk Mail Reporting Program), which is intended to inform us when people are reporting spam sent from our IPs – except, we never get any reports.”

Escalation in February

The issue worsened in February. On Microsoft’s support forums, users began to complain about similar problems as the affected IP range presumably widened. One user wrote:

“We are currently experiencing a critical and recurring email delivery issue affecting recipients at outlook.com, live.com, hotmail.com, and msn.com,” and provided a copy of an error suggesting the mail server has been “temporarily rate limited due to IP reputation.”
Although the error indicates rate limiting, in practice no emails are being delivered.

A large number of users—from the administrator of a server sending automated notifications for Estonian public libraries to an email provider for healthcare professionals—confirmed they were also experiencing delivery problems, and Microsoft support was not helpful.

Impact on Customers

Our reader noted:

“We’ve seen customers struggling to send invoices, order delivery notifications, authentication codes— all sorts, which have been perfectly acceptable to Microsoft/Outlook for many years—now rejected or blocked.”

When a user sees a 550 error, they often assume their own ISP is blocking outgoing email rather than the receiving mail server refusing the message.

“Customers rarely read or understand delivery service notifications—they jump to blaming the ISP or sender, and then head off to find someone else.”

Microsoft’s Response

We asked Microsoft to comment. Apart from acknowledging the questions, the company did not provide further details.

Conclusion

Reducing junk email is commendable, but when a vendor’s error blocks legitimate messages, a rapid and transparent resolution process is essential. Every failed delivery of an invoice or receipt due to over‑zealous or misapplied rules can damage a business’s reputation through no fault of its owner.