قالب وردپرس درنا توس
Home / Tips and Tricks / Microsoft now blocks reply-all email storms in Office 365 and Exchange Online – View Geek

Microsoft now blocks reply-all email storms in Office 365 and Exchange Online – View Geek



  A photo of the Office 365 suite.
dennizn

Reply-all storms can disrupt a business day or destroy a company's email system. They are also unusually annoying, which is why Microsoft introduces a Reply-All Storm Protection feature to its Office 365 and Exchange Online e-mail services.

The new Response-All Storm Protection feature will mostly benefit large companies or organizations with large distribution lists. According to Microsoft, the protection feature is activated after 1

0 responses have been detected to over 5,000 recipients within 60 minutes. When these conditions are met, subsequent answers to the answer-all thread will be blocked for 4 hours. Everyone who tries to respond will receive a receipt that is not delivered and explain the situation.

Small businesses may not benefit from the new protection feature, as it cannot be configured. If you do not have 5,000 addresses in your distribution list, the security feature will not kick in. But over time, Microsoft plans to "fine-tune, fine-tune and improve" the feature to make it more useful in a wider range of Office 365 customers.

According to Greg Taylor from the Exchange team, Answer-All Protection is now enabled for all customers and does not need to be tested or configured. The new feature has been in the works since 2019 and is already reducing the effects of response-all storms within the Microsoft company, which is known to be sensitive to response-all storms.

Source: Microsoft via The Verge [19659008] function (f, b, e, v, n, t, s) {if (f.fbq) return;!? n = f.fbq = function () {n.callMethod.apply n.callMethod (n, argument): n.queue.push (argument)}; if (f._fbq) f._fbq = n; n.push = n; n.loaded = 0; n.version = & # 39; 2.0 & # 39 ;; n.queue !! = []; t = b.createElement (e); t.async = 0 ;! t.src = v; s = b.getElementsByTagName (s) [0]; s.parentNode.insertBefore (t, s)} (window, document, & # 39; script & # 39 ;, & # 39; https: //connect.facebook.net/en_US/fbevents.js'); FBQ (& # 39; init & # 39 ;, & # 39; 1137093656460433 & # 39;); FBQ (& # 39; track & # 39 ;, & # 39; of page view & # 39;);
Source link