{"id":8388,"date":"2019-01-26T00:12:00","date_gmt":"2019-01-25T23:12:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=8388"},"modified":"2021-08-26T13:50:32","modified_gmt":"2021-08-26T11:50:32","slug":"microsoft-employees-experienced-reply-all-email-armageddon","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/01\/26\/microsoft-employees-experienced-reply-all-email-armageddon\/","title":{"rendered":"Microsoft employees experienced reply-all email Armageddon"},"content":{"rendered":"<p><img decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2015\/01\/Stop.jpg\" align=\"left\">[<a href=\"https:\/\/www.borncity.com\/blog\/2019\/01\/25\/microsoft-mitarbeiter-erleben-reply-all-e-mail-lawine\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]Thursday, January 24, 2019, about 11,500 Microsoft employees were probably quite annoyed because their mailboxes were flooded with 'tons of e-mails'. A configuration change to the Microsoft's Github account was the root cause of this incident. <\/p>\n<p><!--more--><\/p>\n<h2>The Bedlam DL3 incident from 2004<\/h2>\n<p>The following tweet mentions a Bedlam DL3 incident, that hit Microsoft employees in 2004. A similar thing occurred on January 24, 2019.&nbsp; <\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"de\">\n<p lang=\"en\" dir=\"ltr\">Someone turned off <a href=\"https:\/\/twitter.com\/github?ref_src=twsrc%5Etfw\">@github<\/a> auto repository following for the Microsoft org. We now have a Bedlam DL3 situation &#8211; <a href=\"https:\/\/t.co\/NCwuedV8NM\">https:\/\/t.co\/NCwuedV8NM<\/a> with people going \"why am I on this email???\" as a reply all. \u200d\u2642\ufe0f<\/p>\n<p>\u2014 An\u017ee Vodovnik (@Avodovnik) <a href=\"https:\/\/twitter.com\/Avodovnik\/status\/1088525033276887040?ref_src=twsrc%5Etfw\">24. Januar 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>  <\/p>\n<p>Bedlam DL3 was <a href=\"https:\/\/blogs.technet.microsoft.com\/exchange\/2004\/04\/08\/me-too\/\" target=\"_blank\" rel=\"noopener\">an incident<\/a> in 2004, where someone set up a mailing list with that name and forwarded it to many Microsoft employees. Many recipients replied that they should be removed from the mailing list. These replies were sent to all participants of the mailing list &#8211; hundreds of thousands of mails were sent to the mailboxes of those concerned. <\/p>\n<h2>The incident on January 24, 2019<\/h2>\n<p>Last Thursday, there was probably a similar incident, as Business Insider reports here. It all started when an employee changed a setting for the company's GitHub account (according to Microsoft employee posts in the social media).<\/p>\n<p>The changed setting caused GitHub to send an automatic message to all recipients of this Microsoft company account. This also included all Microsoft employees working with the Microsoft GitHub account (must be over 11,000 people). The e-mail avalanche had started \u2026 Oh my God. I'm in a reply allpocalypse that stemmed from a GitHub.org notifications thing. The organization in question? Microsoft. <\/p>\n<p>Oh. My. God.<\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"de\"><p>\u2014 Christina Warren is Always on a Plane (@film_girl) <a href=\"https:\/\/twitter.com\/film_girl\/status\/1088521711618805760?ref_src=twsrc%5Etfw\">24. Januar 2019<\/a><\/p><\/blockquote>\n<p><span id=\"preserveb3efd9ffecc747f791612bd006d8533b\" class=\"wlWriterPreserve\"><SCRIPT charset=\"utf-8\" src=\"https:\/\/platform.twitter.com\/widgets.js\" async><\/SCRIPT><\/span> <\/p>\n<p>According to Twitter posts, it didn't take long for some people to commit the mortal sin and respond to this email with a request to be taken off the mailing list. The replies were, of course, distributed to all employees in the Microsoft account.&nbsp; <\/p>\n<p>As a result, some people who notized that, responded with a joke or tried to give help via mailing list answers on how to fix the problem. The employees then found their mailboxes flooded with thousands of e-mails about this process.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]Thursday, January 24, 2019, about 11,500 Microsoft employees were probably quite annoyed because their mailboxes were flooded with 'tons of e-mails'. A configuration change to the Microsoft's Github account was the root cause of this incident.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[1068],"class_list":["post-8388","post","type-post","status-publish","format-standard","hentry","category-office","tag-mail"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/8388","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=8388"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/8388\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=8388"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=8388"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=8388"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}