Yeah, the IT folks in charge of that are doing so at gunpoint. Had someone do that at a giant size corp and the chain of events goes like this.
Email to all gets sent
A few people wonder why they are getting messages not related to their role and reply all to be taken off a list.
Those reply-all get replicated to the same few hundred thousand boxes causing stress on the system.
You well meaning college sends out a reminder via reply-all that you shouldn’t reply-all.
Because those few transactions created somewhere in the order of 2-3 million emails in a short time the servers have a backed up que to chew through causing some people to get things out of order, so maybe they get a ‘take me off the list’ after the fist ‘stop replying all’, now this person decides to help reinforce the ‘stop replying all’ with their own message of the same.
Rinse and repeat until the servers are entirely unable to operate and you need to find a way to flush the cache.
BONUS: Because this is the federal government you can bet that several entities they have contracts with would have automatic relays to distribute incoming messages to required teams for quick responses, so there’s a good chance the effect bleeds into private businesses too because Donnie & Musky will demand that ALL means everyone in the federal contacts list.
Interesting. I’ve never seen that, but I haven’t worked in a company where I’ve needed to send to more than, at most, 15 people at a time.
Probably should be a standard default setting. I wonder what the case for not doing this is? If someone needs to see who is in a group they can usually just open the group in their client and view the emails.
Yeah, the IT folks in charge of that are doing so at gunpoint. Had someone do that at a giant size corp and the chain of events goes like this.
Email to all gets sent
A few people wonder why they are getting messages not related to their role and reply all to be taken off a list.
Those reply-all get replicated to the same few hundred thousand boxes causing stress on the system.
You well meaning college sends out a reminder via reply-all that you shouldn’t reply-all.
Because those few transactions created somewhere in the order of 2-3 million emails in a short time the servers have a backed up que to chew through causing some people to get things out of order, so maybe they get a ‘take me off the list’ after the fist ‘stop replying all’, now this person decides to help reinforce the ‘stop replying all’ with their own message of the same.
Rinse and repeat until the servers are entirely unable to operate and you need to find a way to flush the cache.
BONUS: Because this is the federal government you can bet that several entities they have contracts with would have automatic relays to distribute incoming messages to required teams for quick responses, so there’s a good chance the effect bleeds into private businesses too because Donnie & Musky will demand that ALL means everyone in the federal contacts list.
This man does not bcc
A majority of corporate idiots don’t bcc. That’s why the above happens a lot.
Aaaaallllll the fucking time…
There’s a way in most email environments to setup a mail flow rule that will convert any email with over x number of users CC’d to BCC.
The system must handle the idiots, not the other way around
I’d rather a system that weeds out the idiots
Interesting. I’ve never seen that, but I haven’t worked in a company where I’ve needed to send to more than, at most, 15 people at a time.
Probably should be a standard default setting. I wonder what the case for not doing this is? If someone needs to see who is in a group they can usually just open the group in their client and view the emails.
"why tf did stupid outlook convert my 400 CC’s to BCC THEY SHOULD RESPECT THE USER’S CHOICE