Kernel Data Recovery Blog

Microsoft’s New Reply All Email Storm Protection Feature in Office 365

Read time: 6 minutes

Summary: Replying to every individual email sent through a distribution group is not feasible, especially when there are over thousands of recipients. This could lead to email storm causing disruption in your email system and to handle this, Microsoft has launched “reply all email storm” feature. Let’s learn how does reply all email storm protection helps and how does Kernel Export Office 365 to PST will help in easily backing up Microsoft 365 data.

Office 365 is every professional’s ideal go-to suite of applications due to the countless utilities it offers. However, some of its features might often cause some troubles. One such is Reply All which is an effective feature but has also created nuisance for many companies and their employees leading to the Reply All Email Storms. This can cause heavy damage in the commotion of work for organizations, especially those who do not have proper mail distribution lists.

After so many years, Microsoft is targeting this problem and offering eliminate it completely by rolling out Reply All Storm Protection. Although this is still under improvement but does involve some intricate details that one should know before implementing it. In this article we are going to dig deeper into all the various aspects of Microsoft rolling out the new Email Storm Protection feature in Office 365.

What is Reply All Storm and its protection feature?

When there is a sudden rise of ‘Reply All’ emails on the distribution lists, it creates a long chain of messages. This further multiplies the load of traffic, resulting in an overwhelming email server. This entire situation is the Reply All email storm, also known as Reply Apocalypse.

To protect a workspace from such a disaster, the Reply All Storm Protection feature first detects and then accordingly block the Reply-All messages coming in the same email thread and apply settings which have been set in the first place.

What is the need for protection feature?

There were some incidents which formed the basis for the need of such a feature. It all started when a Microsoft developer was working on creating a new tool in 1997. He created multiple distribution lists and divided all the employees into them. Each list had about 13,000 employees and named it Bedlam DL3. One day an employee found this list and mailed them to remove them from it. Now, this email was received by all the 13,000 members and some of them even sent replies. This created a long chain and each employee’s mailbox was flooded with thousands of emails. Around 15 million emails were sent in an hour, and this led to a crisis which took about 2 days to restore the mailboxes. Many such incidents have been encountered by the companies like Capgemini, GitHub, Utah state government etc.

With this heavy load of incoming messages, the email servers receive much more traffic than usual and can get crashed. This situation can take a few days to often even a week to recover. The organization’s productivity goes for a toss in such a situation. So how can this be resolved and how to safeguard your mailbox from this email storm? Let’s learn about this in detail in the further sections.

Change in settings of Email Storm Protection

To expand the scope of this feature so that more users can take maximum advantage, Microsoft has enabled email admins to customize these settings to make it more specific to their own organization.

If a probable email storm is detected, the protection feature will send a Non-delivery Receipt (NDR) to the sender to immediately stop it from escalating further.
These are the settings and the changes which have been made recently: