It started off with an employee sending an email to a distribution list called "Bedlam DL3" asking to be taken off the list. With 13,000 recipients and everyone replying all with, "Me too!" and other messages, it was estimated that over 15 million messages were sent through the system in an hour. This crashed the MTA service due to a recipient limit. Each time the MTA service recovered, it would attempt to resend the message again which lead to a crash loop.

As a result of the incident, the Exchange team introduced message recipient limits and distribution list restrictions to Exchange, which is something we all use today!

More on the story here: https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643

cross-posted from: https://techy.news/post/2224

It started off with an employee sending an email to a distribution list called "Bedlam DL3" asking to be taken off the list. With 13,000 recipients and everyone replying all with, "Me too!" and other messages, it was estimated that over 15 million messages were sent through the system in an hour. This crashed the MTA service due to a recipient limit. Each time the MTA service recovered, it would attempt to resend the message again which lead to a crash loop.

As a result of the incident, the Exchange team introduced message recipient limits and distribution list restrictions to Exchange, which is something we all use today!

More on the story here: https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643

cross-posted from: https://techy.news/post/2224

It started off with an employee sending an email to a distribution list called "Bedlam DL3" asking to be taken off the list. With 13,000 recipients and everyone replying all with, "Me too!" and other messages, it was estimated that over 15 million messages were sent through the system in an hour. This crashed the MTA service due to a recipient limit. Each time the MTA service recovered, it would attempt to resend the message again which lead to a crash loop.

As a result of the incident, the Exchange team introduced message recipient limits and distribution list restrictions to Exchange, which is something we all use today!

More on the story here: https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643

I recently heard of two stories from friends who were hired as remote or hybrid employees, but later forced to come into the office full-time.

The first friend lives about 50 miles outside of the office and was hired as a remote employee. When the company announced RTO for employees living within a certain radius, he was included because his home fell within the zip code range. He now has to commute over an hour each way to come into the office.

The second friend was recently hired with the expectation of a hybrid schedule to come into the office twice a week. This was discussed and agreed upon by his direct manager and director. During his first week, HR decided to change this and forced all employees to RTO full-time.

IMO, in order to stay truly remote, look for companies that:

• the entire workforce works remote,
• have majority of senior leadership working remote and value working remote, or
• have at least 50% of the workforce working remote without easy access to an office

From M365 Service Health Dashboard:

EX610644

Title: Some users in North America may be unable to access their Exchange Online mailbox using Outlook on the web

User impact: Users in North America may be unable to access their Exchange Online mailbox using Outlook on the web.

More info: Affected users may encounter an unexpected 500 error when accessing Outlook on the web.