{"id":286874,"date":"2023-10-11T20:42:00","date_gmt":"2023-10-11T18:42:00","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=286874"},"modified":"2023-10-24T23:49:18","modified_gmt":"2023-10-24T21:49:18","slug":"exchange-online-strung-ex680695-11-10-2023","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2023\/10\/11\/exchange-online-strung-ex680695-11-10-2023\/","title":{"rendered":"Exchange Online: Störung EX680695 (11.10.2023)"},"content":{"rendered":"

\"Stop[English<\/a>]Zum 11. Oktober 2023 ist es bei Exchange Online zu einer schweren St\u00f6rung des Mail-Verkehrs gekommen. Mehrere Leser berichteten von Problemen beim Empfang von E-Mails von externen E-Mail-Adressen. Microsoft hat den Vorfall best\u00e4tigt und will bereits einen Fix ausgerollt haben. Spoiler: Die sind Opfer des eigenen SPAM-Schutzes geworden, den man zum Patchday ausrollte.<\/p>\n

<\/p>\n

\"\"Ich wurde heute gleich von mehren Nutzern bez\u00fcglich der St\u00f6rung informiert (danke daf\u00fcr), kann aber erst jetzt reagieren, da ich unterwegs war. Christoph Z. schrieb zum Beispiel:<\/p>\n

Probleme mit M365 Exchange Online<\/p>\n

Hallo,<\/p>\n

Bei unseren Kunden mit M365 Exchange Online treten heute vermehrt Probleme beim Empfang von E-Mails von externen E-Mail-Adressen auf. Offenbar liegt eine St\u00f6rung seitens Microsoft vor.<\/p>\n

\"Microsoft is reporting a service issue that is causing delivery delays for email coming from outside our organization. Microsoft has identified the cause of the issue and is in the process of deploying a fix. \"<\/p>\n

Vielleicht haben Ihre Leser auch Probleme mit Exchange Online.<\/p><\/blockquote>\n

Andere Leser hatten diese Probleme ebenfalls. Steffen H. meldete sich und schrieb dazu:<\/p>\n

Guten Tag Herr Born,<\/p>\n

ich w\u00fcrde Sie nur gerne \u00fcber aktuelle Probleme mit dem Exchange Online von Microsoft informieren, sofern noch nicht bekannt.<\/p>\n

Es kommt aktuell dazu das Mails welche Richtung Exchange Online gesendet werden von MS nicht angenommen werden.<\/p>\n

Diese verbleiben in der E-Mail-Warteschlange unseres NoSpamProxy's.<\/p>\n

Grund: \u201e451 4.7.500 Server busy\"<\/p>\n

Im Admin Center gibt es ebenfalls einen entsprechenden Eintrag\/Vorfall dazu.<\/p><\/blockquote>\n

<\/p>\n

Thomas W. hat per Mail folgende Infos geliefert:<\/p>\n

seit heute morgen gibt es erhebliche Probleme mit Exchange Online.<\/p>\n

Auf unseren MTAs h\u00e4ngen hunderte E-Mails an Empf\u00e4nger bei Exchange Online.<\/p>\n

Microsoft best\u00e4tigt es telefonisch, aber keine offizielle Kommunikation…<\/p><\/blockquote>\n

Er verwies auf einen reddit.com-Post<\/a>, wo entsprechendes ebenfalls zu lesen ist. Thomas Z. schrieb mir dazu:<\/p>\n

Hallo Herr Born,<\/p>\n

auf unserem mx4.tz-com.at (78.47.134.189) habe ich seit heute 5:29 Uhr > 400 E-Mails h\u00e4ngen die an M365 gehen sollen. Hier senden unsere Kunden alle E-Mails via Relay weg. Unser Server ist auf keiner Blacklist zu finden.<\/p>\n

Alle Meldungen lt. Log ziemlich gleich
\n——- cut ——-
\n451 4.7.500 Server busy. Please try again later from [x.x.x.x]. (S77719) [DBAEUR03FT016.eop-EUR03.prod.protection.outlook.com 2023-10-11T13:37:42.355Z 08DBC945E7F99585]
\n<xxx@xxx.com>… Deferred: 451 4.7.500 Server busy. Please try again later from [x.x.x.x]. (S77719) [DBAEUR03FT016.eop-EUR03.prod.protection.outlook.com 2023-10-11T13:37:42.355Z 08DBC945E7F99585]
\nClosing connection to xxxx.mail.protection.outlook.com.<\/p><\/blockquote>\n

Thomas verwies auf diesen Beitrag<\/a> bei Microsoft, wo ein Administrator das Problem ebenfalls gemeldet hat. Andreas P. hat mir wie immer die betreffenden Ausz\u00fcge Microsofts im Admin-Statusbereich per Mail geschickt:<\/p>\n

Published Time: 11.10.2023 19:11:15
\nWe've completed development of an additional fix which is undergoing validation prior to deployment. We expect to complete this process within the next 60 minutes.
\nThis quick update is designed to give the latest information on this issue.<\/p>\n

Published Time: 11.10.2023 18:27:35
\nTitle: Some users may encounter delays receiving external email messages in Exchange Online
\nUser impact: Users may encounter delays receiving external email messages in Exchange Online.
\nMore info: Impact is specific to Simple Mail Transfer Protocol (SMTP), and users may encounter delays of up to 24 hours. Additionally, the email sender may receive a Non-Delivery Report (NDR) with a \"451 4.7.500 Server busy\" error message, and their attempt to retry delivery of the email may be delivered up to 24 hours later.
\nCurrent status: We've determined that our previous developed fix to resolve the throttling issue has proven to be unsuccessful. We're developing a new fix that will undergo internal validation to ensure it resolves the underlying issue before deploying it to the impacted environments.<\/p>\n

Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
\nStart time: Monday, October 9, 2023, at 9:00 PM UTC
\nRoot cause: A recent service update, applied to a section of infrastructure responsible for enforcing IP address anti-spam rules, contains a change which is causing impact.
\nNext update by: Wednesday, October 11, 2023, at 6:30 PM UTC<\/p>\n

Published Time: 11.10.2023 12:26:01
\nTitle: Some users may encounter delays receiving external email messages in Exchange Online
\nUser impact: Users may encounter delays receiving external email messages in Exchange Online.
\nMore info: Affected users may see a \"451 4.7.500 Server busy\" error message.
\nCurrent status: We've identified that specific IP addresses are being unexpectedly limited by our anti-spam procedures, causing inbound external email delivery to become throttled and delayed. We're reviewing if there have been any recent changes to our anti-spam rules to understand why the IP addresses are being limited. In the meantime, we're manually adding reported affected IP addresses to an allowed list to provide immediate relief.
\nScope of impact: Impact is specific to some users who are served through the affected infrastructure.
\nNext update by: Wednesday, October 11, 2023, at 12:30 PM UTC<\/p>\n

Published Time: 11.10.2023 10:59:51
\nTitle: Some users may encounter delays receiving external email messages in Exchange Online
\nUser impact: Users may encounter delays receiving external email messages in Exchange Online.
\nMore info: Affected users may see a \"451 4.7.500 Server busy\" error message.
\nCurrent status: We're analyzing sample throttling IPs from simple messages to confirm whether the issue with the portion of SQL infrastructure is causing impact, before we begin formulating a remediation plan.
\nScope of impact: Impact is specific to some users who are served through the affected infrastructure.
\nNext update by: Wednesday, October 11, 2023, at 11:00 AM UTC<\/p>\n

Published Time: 11.10.2023 08:33:49
\nTitle: Users are unable to receive external email messages within Exchange Online
\nUser impact: Users are unable to receive external email messages within Exchange Online.
\nMore info: Some users email messages may send; however, users may experience delays up to one hour.
\nCurrent status: Our review of simple messages has lead us to a potential root cause where a portion of SQL infrastructure may be receiving an unusually large number of requests that may be hindering Exchange Online's performance. We're working to confirm our findings to cultivate further troubleshooting steps.
\nScope of impact: Your organization is impacted by this event, as well as users who are attempting to receive external email messages within Exchange Online.
\nNext update by: Wednesday, October 11, 2023, at 8:30 AM UTC<\/p>\n

Published Time: 11.10.2023 06:52:50
\nTitle: Users are unable to receive external email messages within Exchange Online
\nUser impact: Users are unable to receive external email messages within Exchange Online.
\nCurrent status: We're currently reviewing simple messages to refine our understanding of this specific impact scenario and establish our troubleshooting steps.
\nScope of impact: Your organization is impacted by this event, as well as users who are attempting to receive external email messages within Exchange Online.
\nNext update by: Wednesday, October 11, 2023, at 6:30 AM UTC<\/p>\n

Published Time: 11.10.2023 06:22:26
\nTitle: Users are unable to receive external email messages within Exchange Online
\nUser impact: Users are unable to receive external email messages within Exchange Online.
\nCurrent status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.<\/p><\/blockquote>\n

Microsoft ist Opfer seines Anti-Spam-Updates geworden. Ein k\u00fcrzlich durchgef\u00fchrtes Service-Update f\u00fcr einen Teil der Infrastruktur, der f\u00fcr die Durchsetzung der Anti-Spam-Regeln f\u00fcr IP-Adressen zust\u00e4ndig ist, enthielt eine \u00c4nderung, die diese Auswirkungen verursachte. Das Problem sollte nun behoben sein.<\/p>\n

Immer wieder sch\u00f6n zu lesen, wie die Cloud-L\u00f6sungen mit Exchange Online da weltweit Administratoren in Atem halten. Ganz p\u00f6se Zungen fl\u00fcstern, dass wenige Stunden vorher Patchday bei Microsoft war und On-Premises Exchange Server Updates bekamen, die Probleme verursacht haben. Obiger Vorfall bezieht sich aber auf Exchange Online, da sorgt Microsoft f\u00fcr Patches und reibungslosen Betrieb \u2013 ist jedenfalls das Argument, was man so landl\u00e4ufig h\u00f6rt.<\/p>\n

Vielleicht ist das die \"ausgleichende Gerechtigkeit\" des Administratoren-Gotts, der sah, wie Exchange On-Premises Admins leiden und beschloss, da auch mal einen Blitz in die Cloud zur Exchange Online-Fraktion zu schleudern. Der Einschlag war scheinbar gut zu h\u00f6ren, hat mich aber heute so gar nicht gest\u00f6rt<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

[English]Zum 11. Oktober 2023 ist es bei Exchange Online zu einer schweren St\u00f6rung des Mail-Verkehrs gekommen. Mehrere Leser berichteten von Problemen beim Empfang von E-Mails von externen E-Mail-Adressen. Microsoft hat den Vorfall best\u00e4tigt und will bereits einen Fix ausgerollt haben. … Weiterlesen →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7263,7862],"tags":[1171,7211,987],"class_list":["post-286874","post","type-post","status-publish","format-standard","hentry","category-cloud","category-stoerung","tag-cloud","tag-exchange-online","tag-storung"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/286874","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=286874"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/286874\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=286874"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=286874"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=286874"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}