cross-posted from: https://feddit.online/c/tech@feddit.online/p/2115831/microsoft-365-outage-leads-to-chlorine-gas-poisoning-of-15-hotel-guests
cross-posted from: https://feddit.online/c/tech@feddit.online/p/2115831/microsoft-365-outage-leads-to-chlorine-gas-poisoning-of-15-hotel-guests
The technical standards for Email would allow for 3 days of delivery failure before finally giving up. That’s the amount of leeway email has (in theory - practically we assume that everything longer than 3 minutes means something has gone wrong). Sending alerts by email is fine for non-critical applications; if one of my docker containers crash, an email is fine because the amount of damage is nil.
Why wasn’t there an actual fail-safe mechanism employed that measures the chlorine levels and shuts the whole thing down BEFORE it gets dangerous?
This is not a Microsoft problem. This is a negligence problem on Phantasialands side, using inappropiate tools for a system that can hurt people on failure, and should be followed up by lawsuits.
From: noreply@carbondioxidedetector.com.au
RE: Carbon Dioxide leak detected
Message: To whom it may concern, an elevated carbon dioxide level was measured in the walk-in fridge in the bar kitchen. Probably one of the keg lines is leaking pressurised gas. Gas PPM is classified as alert level 5 - Immediately harmful to life. Please evacuate staff from the area and ventilate the fridge thoroughly before attempting entry with ELSRD hood donned to shut down gas flow.
Folder: Spam
Yeah
“Why do all our alerts go to spam”
Oh, well everyone just ignores them, then Jeff who isn’t even on the IT team but was on the mailing list was getting them. So Jeff marked them as spam instead of asking to be removed from the mail list, and now our corporate email provider just black holes them.