The correct response is to reply all when people start bitching. I can usually throw in an “unsubcribe” request in a separate email.
Semi_Hemi_Demigod@lemmy.world 12 hours ago
I worked for a startup that got bought by Oracle. Five whole years without a reply-all storm, but the first week we had hundreds of people reply all and it was hilarious watching the admins try and fail to convince people to stop replying all.
bitchkat@lemmy.world 6 hours ago
CarbonatedPastaSauce@lemmy.world 11 hours ago
Wonder what the back end software is there. With Exchange reply-all storms are a thing of the past. I don’t have to convince anyone of anything to stop a reply all storm. Takes 2 minutes of setting up a transport rule. But the admin needs to be experienced enough to know that.
Semi_Hemi_Demigod@lemmy.world 11 hours ago
It was Oracle so they probably have a terrible internal email server that will have reply-all storm protection in a year or two.
I was working with the customer service software devs to migrate my team from Salesforce’s Desk.com (because Oracle hates Salesforce) and they said it would take 18 months to make a dropdown that you could type in and select a macro for a ticket. Eventually they gave up.
bitchkat@lemmy.world 6 hours ago
I just talked to an oracle employee. They are using outlook/exchange/teams now and have moved on from Beehive.
slazer2au@lemmy.world 10 hours ago
Is there any other way to describe Lotus?
CarbonatedPastaSauce@lemmy.world 11 hours ago
Enough said. You have my sympathy.
purplemonkeymad@programming.dev 7 hours ago
I’ve pointed out that this issue could arrise so many times to companies with the all staff email. Every time they push back on wanting to define limited senders, “we don’t think it’s an issue/no one would do that!” Until someone sends an inappropriate email to the whole company, then it’s suddenly IT’s fault.