字号·· | 护眼
theregister

Outlook.com退回合法电子邮件,微软身份验证整顿行动出现偏差Outlook.com bounces legit emails as Microsoft's authentication crackdown goes sideways

点「原文对照」整页切到原文,或双击某段只看那段的原文。

验证错误导致 Outlook.com 无法接收合法邮件。该问题似乎影响范围广泛,据受影响用户反馈,可能导致无法投递报告,错误代码与 SPF(发件人策略框架)验证失败有关。其他用户报告的错误则提示缺少 DMARC(基于域的消息认证、报告和一致性)信息。故障始于上周末,似乎是微软收紧了(或至少试图收紧)接收邮件的规则所致。

A validation error has stopped Outlook.com from accepting legitimate emails. The problem appears widespread and, according to reports from affected users, can result in non-delivery reports with error codes related to SPF (Sender Policy Framework) validation failures. Other users have reported errors highlighting a lack of DMARC (Domain-based Message Authentication, Reporting, and Conformance) information. The troubles began at the end of last week and appear to be the result of Microsoft tightening the rules (or at least attempting to do so) for accepting emails.

该公司的消费者电子邮件服务受到影响,目前看来,如果域名没有有效的 SPF,或者缺少 DMARC 记录,Outlook.com 及同类服务就会将其视为可疑并拒收邮件。这些规则旨在应对垃圾邮件、批量发件人等问题。2025 年,微软宣布新规则,旨在加强每天发送超过 5,000 封邮件的域名的邮件认证。除了要求符合 DMARC 和 SPF 外,还要求使用 DKIM(域名密钥识别邮件)。

The company's consumer email services are affected, and it appears that if a domain doesn't have working SPF or if it has a missing DMARC record, then Outlook.com and its ilk will treat it as suspicious and not accept emails. The rules are designed to deal with spam, bulk senders, and the like. In 2025, Microsoft announced new rules designed to strengthen email authentication for domains sending more than 5,000 emails per day. In addition to DMARC and SPF compliance, DKIM (DomainKeys Identified Mail) was also required.

尽管这似乎是阻止垃圾邮件发送者的好主意,但小规模发件人现在似乎也受到了影响。根据 Outlook 论坛上的投诉者反映,一封只有一行内容的单封邮件现在可能就会被拒收。此外,微软尚未发布任何通告向客户解释规则有何变化。虽然部分客户坚称其 DMARC、SPF 和 DKIM 设置符合要求,但更多用户反映,一旦按微软的要求进行设置,邮件便恢复正常收发。

Although this seemed like a good idea to ward off spammers, small senders now appear to be affected. According to complainants in the Outlook forum, a single email with just one line might now be rejected. Furthermore, Microsoft has not issued any advisory to customers explaining how the rules have changed. Although some customers insist their DMARC, SPF, and DKIM settings are compliant, many more have reported that once they set them to Microsoft's requirments, email began flowing once more.

SPF 必须针对发件域名通过验证(该域名的 DNS 记录应准确列出授权的 IP 地址/主机)。DKIM 必须通过验证以确保邮件的完整性和真实性。DMARC 至少应设为 p=none,并与 SPF 或 DKIM 对齐(最好两者都对齐)。我们已向这家 Windows 巨头询问更多信息,但截至发稿尚未收到回复。

SPF must pass for the sending domain (the domain's DNS record should accurately list authorized IP addresses/hosts). DKIM must pass to validate email integrity and authenticity. DMARC must have at least p=none and align with either SPF or DKIM (preferably both). The asked the Windows giant for more information, but we have yet to receive a response.

雪上加霜的是,这个故障似乎还具有间歇性。重新发送的尝试可能会在遭到拒绝后成功。更糟糕的是,拒绝错误信息对于最初导致邮件退回的原因可能也语焉不详。微软支持论坛的一名版主承认了这一漏洞,并表示它被“归类为服务降级”。“微软正在积极调查此次电子邮件投递问题的根本原因,工程团队正在积极分析服务遥测数据和客户提供的数据,以确定问题根源。”尽管如此。

To make matters worse, the glitch also appears to be intermittent. A resend attempt might succeed following a rejection. To compound the situation, the rejection error message may also be vague about what caused the bounce in the first place. A moderator in Microsoft's support forum acknowledged the bug and said it was "classified as a service degradation." "Microsoft is actively investigating the underlying cause of this email delivery issue, and engineering teams are actively analyzing service telemetry and customer-provided data to identify the source of the issue."

情况可能本会更糟。今天早些时候,欧洲、中东和非洲的几位用户受到了微软的另一个失误的影响——一项“近期服务变更”导致部分连接被突然中断。网页版 Outlook 以及 Purview 和 Defender 门户网站均受到影响。微软回滚了 Exchange Online 前端基础设施中的这项变更,一切恢复正常。该公司尚未说明其电子邮件服务中是否还有其他可能导致合法邮件被退回的变更(如果有的话)。

Still. It could be worse. Earlier today, several users in Europe, the Middle East, and Africa were affected by another Microsoft whoopsie – a "recent service change" that caused some connections to be abruptly terminated. Outlook on the web, as well as the Purview and Defender portals were all affected. Microsoft reverted the change in the Exchange Online front-end infrastructure, and all was well.

® 11月10日世界协调时0922更新 微软已证实这是一个故障。该公司在其事件报告(EX1545193)中写道:“近期对垃圾邮件执行规则的更新导致电子邮件被错误标记和阻止,从而造成了影响。”该公司还表示将审查其更新程序。对于因微软的最新失误而发现合法邮件被其服务器拒绝的客户来说,这将会带来极大的慰藉。感谢 DMARKOFF 的 Aliaksandr Markau 提供线索。

It has yet to say what else, if anything, might have changed in its email services to cause legitimate messages to bounce back. ® Updated to add at 0922 UTC, November 10 Microsoft has confirmed that this was a fault. In its incident report (EX1545193), the company wrote: "A recent update to the spam enforcement rules caused email messages to be incorrectly marked and blocked, which led to impact." It also said it would review its update procedures. This will be of great comfort to customers who found legitimate emails rejected by Microsoft's servers as a result of the latest whoopsie. Thanks to Aliaksandr Markau at DMARKOFF for the tip.

阅读媒体原文 ↗