This is purely anecdotal, but I am seeing far fewer replyallpocalypses than I did 10-15 years ago. Has something changed, like better server or client email software? Or perhaps admins and users are more savvy about avoiding this kind of behavior? (Maybe I've just been lucky to not have to deal with one of these for several years.)
When I’m Mistakenly on an Email Chain, Should I Reply All Asking to Be Removed?
31–40 of 46 posts
Re: When I’m Mistakenly on an Email Chain, Should I Reply All Asking to Be Removed?
#32Still NO.
Re: When I’m Mistakenly on an Email Chain, Should I Reply All Asking to Be Removed?
#33This is purely anecdotal, but I am seeing far fewer replyallpocalypses than I did 10-15 years ago. Has something changed, like better server or client email software? Or perhaps admins and users are more savvy about avoiding this kind of behavior? (Maybe I've just been lucky to not have to deal with one of these for several years.)
Maybe some MTAs now warn if a message is going to be sent to a large number of people? A simple "This message is going to be sent to 15,000 people, are you sure you want to send it?" message would work wonders I bet.
Re: When I’m Mistakenly on an Email Chain, Should I Reply All Asking to Be Removed?
#34Relevant Wikipedia page, since the article is completely lacking in historical context: https://en.wikipedia.org/wiki/Email_storm "On 14 October 1997, a Microsoft employee noticed that they were on an as-yet unknown email distribution list 'Bedlam DL3', and emailed the list asking to be removed. This list contained approximately a quarter of the company's employees, 13,000 email addresses. Other users replied to the…
This happened a few times at the bank I worked at for almost a decade. You could count on the technologists to not throw gas on the fire by replying (everyone'd heard of Bedlam DL3), but once non-technical sales, trading and ops were on the list, all bets were off.
Re: When I’m Mistakenly on an Email Chain, Should I Reply All Asking to Be Removed?
#35Couldn't an "unsubscribe" functionality be written into an email server? You'd have to change the way mailboxes are stored. In particular, email threads and recipients lists would have to become explicit objects in a distributed database. Perhaps threads could be identified by a canonicalized version of the original recipients list, plus some other information?
Or you could just reply to the list itself with the word 'remove' in the subject (doesn't work for all list servers). That's how most servers handled subscriptions back in the days and probably still is now.
Re: When I’m Mistakenly on an Email Chain, Should I Reply All Asking to Be Removed?
#36Re: When I’m Mistakenly on an Email Chain, Should I Reply All Asking to Be Removed?
#37Why does such an email list even exist? For some kind of HR emergency? Aren't there other emergency messaging systems that could be more effective?
Re: When I’m Mistakenly on an Email Chain, Should I Reply All Asking to Be Removed?
#38At a former job someone sent a completely inane email asking about something personal to an HR email list or all people in the company, about 21,000 people. Why does such an email list even exist? For some kind of HR emergency? Aren't there other emergency messaging systems that could be more effective?
Re: When I’m Mistakenly on an Email Chain, Should I Reply All Asking to Be Removed?
#39This is purely anecdotal, but I am seeing far fewer replyallpocalypses than I did 10-15 years ago. Has something changed, like better server or client email software? Or perhaps admins and users are more savvy about avoiding this kind of behavior? (Maybe I've just been lucky to not have to deal with one of these for several years.)
Re: When I’m Mistakenly on an Email Chain, Should I Reply All Asking to Be Removed?
#40Relevant Wikipedia page, since the article is completely lacking in historical context: https://en.wikipedia.org/wiki/Email_storm "On 14 October 1997, a Microsoft employee noticed that they were on an as-yet unknown email distribution list 'Bedlam DL3', and emailed the list asking to be removed. This list contained approximately a quarter of the company's employees, 13,000 email addresses. Other users replied to the…
This happened a few times at the bank I worked at for almost a decade. You could count on the technologists to not throw gas on the fire by replying (everyone'd heard of Bedlam DL3), but once non-technical sales, trading and ops were on the list, all bets were off.