No matter how hard you work, you’re probably going to get laid off anyway. So don’t sweat it.
It’d be funny if this is just a Charlie in the mailroom incident and someone at Outlook found out they were getting fired.
Be fun if they held it hostage. Don’t bring email back up until demands are met. Worker ownership. CEO exiled to a remote island.
Pretty sure he’s been to remote islands before
Little St Nick’s is really not remote at all
c/woooosh
This was the opportunity I was hoping they’d take advantage of! I have no idea what the labor organizing looks like inside, but I bet it’s heavily monitored.
Been a very long time since I worked in IT, but I’m pretty sure at least some mail servers are configured to give up the attempt to deliver sent emails after x number of attempts have failed. Not 100% on this since mail wasn’t my thing, but I seem to vaguely recall that. If I’m right, then the emails most certainly are going somewhere - the “undelivered” graveyard.
The RFC recommends that it should be retried for 5 days. Which is also the default in most mail servers.
However, many larger mail providers, including Microsoft, only do a single day before the mail bounces.
I wonder if this experience makes them reconsider keeping to the RFC recommendation.
I find the idea of Microsoft even considering following an open standard to be laughable on the face of it.
Yeah, that’s rather untypical for them.
Must be why the front fell off of Exchange.
Embrace, extend.
That could be a hacker movie plot.
“Oh no, the bad guy sent the info in an email! I know, let’s crash the servers until it gets undeliverable!”
Microsoft overrode the 24 hour limit to 48 hours to give themselves more time.
But send side from outside MSFT isn’t in their control.
You make it sound like that’s a bad thing 😅
This is marginally related but proton has a feature that tells when you when an email is still being retried, and when it gives up.
That email is called something like delayed mail (still being retried), and for a long time, my dumbass thought it was some feature that was being retired and I was like wtf why have they taken months to retire this feature.
Anyway, proton retries for 48 hrs as well.
Can’t smtp do multiple hops through multiple smtp servers or MX (mail exchanges)? In which case, how would the client know, beyond the first hop?
First every hour, then every two, four, eight and then like once day for a a week . After that you get a ‘could not deliver this message’.
At least, that is how I setup my servers…
Just inbox zero on Monday, aka trash all
Monday? Make it Tuesday for a truly well earned weekend.
Also, a good alternative is LibreOffice. Or Euro Office.
Libreoffice has an email client?
No, for word/excel/powerpoint.
For email clients you could go for Nextcloud, that’s a suite. Or Mailbox. Tuta’s good too but their UI might need improvement & their policies could be refined more.
So how does Libreoffice help with this?
to the Microsoft employees desperately trying to bring Outlook back online…
Just shut up with your logic and switch to Linux.
Already did, years ago
So it must have fixed Outlook’s mail service being down, years ago.
This whole thread is extremely funny to me for no good reason
Why not just thunderbird?
But anyway, what happened here is not a client issue. I’m guessing some people just saw “outlook” in the recent headlines and didn’t understand it’s a service issue not a client app issue.
I don’t think Thunderbird hosts mail addresses
