EWS is the only realistic way for "not Outlook" to work - MAPI is not exactly an open API.
When EWS goes away so will rather a lot of customers, probably not enough to dent the bottom line (initially).
Then it becomes apparent that all email is equal and Exchange online becomes a footnote in history. Microsoft used to do email and then they shat the bed. All a bit embarrassing on the surface but not really.
Running email systems is a right old pain when all you really desire is data (and metadata) to mine and flog on to other data fetishists. Email is generally rather static and rather large in storage terms but it can yield gold from personal exchanges.
Ideally you get someone else to take the pain (AWS, Google and co - yes they get to mine but they bear the costs too) but ensure the marks use Outlook (and they do).
Then you change Outlook (loving the new Electron version) to store all credentials in your cloud. You use those creds to mine data within email held on other people's clouds. They front the cost of storage.
> At present, EWS is our best way to enable support for both Exchange Online and on-premise installations.
> Graph API has been considered and may be considered again in future, but it currently provides narrower support than EWS and lacks some functionality for desktop applications. Even with the announcement that EWS support will be removed for Exchange Online, it's still valuable in the short term for enabling access for a wide userbase and in the long term for supporting users using on-premise installations.
Strategically this makes sense if the goal is just to get people to use Thunderbird, but ideologically JMAP support would be a lot nicer in my opinion.
I recently tried Thunderbird instead of Outlook. It had the same issue as FF did before the quantum update: It's too damn slow. Switching between different folders with hundreds or thousands of mails has noticable delays, while in Outlook it's essentially instant.
I have exactly the opposite experience. Using outlook for mail is such a pain to me. Particularly the search experience does not work (I use expressionsearchNG for thunderbird) . For calendars it is just the opposite so that I am currently running it side by side. One problem is I think the iCal bridge to the outlook server we have to use at work. The announcement unfortunately cannot change anything here. I used the EWS addon maintained by Ericson [1] for a while. But Mozilla I guess drove many Plugin developers away by breaking the interface rapidly. Now they are putting some stuff into the core again. I am not really sure if that is a good strategy. They should rather IMHO work on a stable interface.
Yeah, and have your email appear significantly worse on a bunch of email clients all in the name of tech purism / nostalgia for ‘the old days’.
After I saw how usual it was for plain text email to be rendered in a fixed-width font, instead or something more sane, there’s no way I could justify doing it just because “HTML email is an abomination” or whatever.
>in the entire 20 year lifetime of the Thunderbird project, no one has added support for a new mail protocol before.
Technically true but also every megacorp's OAuth2 out-of-band authentication implementation needs it's own special configuration (read workaround) per email client and Thunderbird has collected quite a few. These are not normal mail protocols: they're over HTTPS not IMAP or POP3 or SMTP.
This proclamation "no one has added support for a new mail protocol" is a good thing and this change is not good. Supporting proprietary setups is pragmatic and understandable but it's not good. This is only going to briefly mitigate the problems of email splintering into dozens of per-corporation variations while encouraging people to be okay with them in the long run.
Not sure why the headline was changed. This is an article about Rust programming. "Bringing Exchange Support to Thunderbird" implies it's about Thunderbird and it's support for Exchange - something you won't learn from the article.
Based on the first paragraph of the article which focuses on Exchange rather than language, I'd say the feature itself is more important than the implementation, and that's also what most users care about.
I guess support for proprietary specifications is useful, but I really wish Mozilla would prioritise implementing standards like auto-discovery of email submission (SMTP) servers (rfc6186, 2011).
Currently, users have to manually provide hostname and port of their SMTP server, which is likely fine for those of us on this website, but not at all friendly for the other 99.9% of the human population.
The amount of effort require to implement all of Exchange is also probably orders of magnitude more than discovery of submission servers via DNS/SRV. I really don't get Mozilla's priorities.
> Currently, users have to manually provide hostname and port of their SMTP server
i don't think I had to do that when I added my Hotmail, Google, or Yahoo accounts to Thunderbird. I just used my email address at each of them. Are these treated as special cases?
Wow! 20 years or so ago, I remember working in IT and only a few of us ran Linux in otherwise fully Microsoft shops. Exchange was always one of these things that it was tough to find a good client for. We would have been over the moon!
Using anything Microsoft on Linux is really painful, and they appear to be in the process of deprecating the web version of Teams if you're not specifically using Edge :(
> There was also no paid maintainership from about 2012 — when Mozilla divested and transferred ownership of Thunderbird to its community — until 2017, when Thunderbird rejoined the Mozilla Foundation.
What a scandal this was. A prime example of Mozilla's backwards priorities.
I disagree. The world moved to web/mobile app based mail. You’re allowed to not be happy about that (I’m not over the moon about it) but it’s the truth. It wasn’t worth Mozilla funding it.
Please include PST file import out of the box so that folks can seamlessly switch away from their Outlook installs without having to fiddle with Outlook itself. There is a free project for reading PST files, all it needs is integrating into the suite.
(The big differences are IMAPv4r2 mandates a lot of necessary new features, like UID or UTF-8 support, and actually deprecated silly old stuff like MUTF7 mailbox names.)
It's not bad - their time range narrowing graph thingy is really good, and I can normally find what I need. My main complaint is that my outlook calendars don't show up, so I can't search them for events.
I've been using thunderbird in exchange places for years. Yeah, it's shit, but that's exchange. I just try to limit my exposure. But I can see "invites" and that kind of stuff. What am I missing?
Are you suggesting that no development is justified? I think we can expect that for any email client, there will be demand for one of the most popular email servers, and one that is required for most corporate use.
[+] [-] lousken|1 year ago|reply
[+] [-] gerdesj|1 year ago|reply
When EWS goes away so will rather a lot of customers, probably not enough to dent the bottom line (initially).
Then it becomes apparent that all email is equal and Exchange online becomes a footnote in history. Microsoft used to do email and then they shat the bed. All a bit embarrassing on the surface but not really.
Running email systems is a right old pain when all you really desire is data (and metadata) to mine and flog on to other data fetishists. Email is generally rather static and rather large in storage terms but it can yield gold from personal exchanges.
Ideally you get someone else to take the pain (AWS, Google and co - yes they get to mine but they bear the costs too) but ensure the marks use Outlook (and they do).
Then you change Outlook (loving the new Electron version) to store all credentials in your cloud. You use those creds to mine data within email held on other people's clouds. They front the cost of storage.
Smashing.
[+] [-] babolivier|1 year ago|reply
> At present, EWS is our best way to enable support for both Exchange Online and on-premise installations.
> Graph API has been considered and may be considered again in future, but it currently provides narrower support than EWS and lacks some functionality for desktop applications. Even with the announcement that EWS support will be removed for Exchange Online, it's still valuable in the short term for enabling access for a wide userbase and in the long term for supporting users using on-premise installations.
[+] [-] mairusu|1 year ago|reply
[+] [-] shamiln|1 year ago|reply
[+] [-] hnarn|1 year ago|reply
[+] [-] ocdtrekkie|1 year ago|reply
[+] [-] Semaphor|1 year ago|reply
[+] [-] eholk|1 year ago|reply
[+] [-] riedel|1 year ago|reply
[1] https://github.com/Ericsson/exchangecalendar
[+] [-] avidphantasm|1 year ago|reply
[+] [-] cqqxo4zV46cp|1 year ago|reply
After I saw how usual it was for plain text email to be rendered in a fixed-width font, instead or something more sane, there’s no way I could justify doing it just because “HTML email is an abomination” or whatever.
[+] [-] superkuh|1 year ago|reply
Technically true but also every megacorp's OAuth2 out-of-band authentication implementation needs it's own special configuration (read workaround) per email client and Thunderbird has collected quite a few. These are not normal mail protocols: they're over HTTPS not IMAP or POP3 or SMTP.
This proclamation "no one has added support for a new mail protocol" is a good thing and this change is not good. Supporting proprietary setups is pragmatic and understandable but it's not good. This is only going to briefly mitigate the problems of email splintering into dozens of per-corporation variations while encouraging people to be okay with them in the long run.
[+] [-] fabrice_d|1 year ago|reply
On the other hand, being able to use Thunderbird as a client is a net win and a pragmatic move.
[+] [-] wolverine876|1 year ago|reply
It's not just one of every megacorp, it's by far the most commonly used email in business, Microsoft's Exchange and especially Exchange online.
[+] [-] bachmeier|1 year ago|reply
[+] [-] pquki4|1 year ago|reply
[+] [-] ktosobcy|1 year ago|reply
[+] [-] Zhyl|1 year ago|reply
[+] [-] WhyNotHugo|1 year ago|reply
Currently, users have to manually provide hostname and port of their SMTP server, which is likely fine for those of us on this website, but not at all friendly for the other 99.9% of the human population.
The amount of effort require to implement all of Exchange is also probably orders of magnitude more than discovery of submission servers via DNS/SRV. I really don't get Mozilla's priorities.
[+] [-] kwhitefoot|1 year ago|reply
i don't think I had to do that when I added my Hotmail, Google, or Yahoo accounts to Thunderbird. I just used my email address at each of them. Are these treated as special cases?
[+] [-] Schnitz|1 year ago|reply
[+] [-] small_scombrus|1 year ago|reply
Using anything Microsoft on Linux is really painful, and they appear to be in the process of deprecating the web version of Teams if you're not specifically using Edge :(
[+] [-] anonzzzies|1 year ago|reply
[+] [-] ForHackernews|1 year ago|reply
What a scandal this was. A prime example of Mozilla's backwards priorities.
[+] [-] afavour|1 year ago|reply
[+] [-] zozbot234|1 year ago|reply
[+] [-] DaiPlusPlus|1 year ago|reply
EDIT: Oh, nvm - it's on-prem only - huh... that's asinine.
[+] [-] rdl|1 year ago|reply
[+] [-] AnonC|1 year ago|reply
[+] [-] packetlost|1 year ago|reply
[+] [-] jcranmer|1 year ago|reply
(The big differences are IMAPv4r2 mandates a lot of necessary new features, like UID or UTF-8 support, and actually deprecated silly old stuff like MUTF7 mailbox names.)
[+] [-] f_devd|1 year ago|reply
[+] [-] sega_sai|1 year ago|reply
[+] [-] Scarbutt|1 year ago|reply
[+] [-] promiseofbeans|1 year ago|reply
[+] [-] diarrhea|1 year ago|reply
[+] [-] akvadrako|1 year ago|reply
[+] [-] globular-toast|1 year ago|reply
[+] [-] Neil44|1 year ago|reply
[+] [-] barfard|1 year ago|reply
[deleted]
[+] [-] florid|1 year ago|reply
[deleted]
[+] [-] jaylittle|1 year ago|reply
[+] [-] gtech1|1 year ago|reply
[+] [-] counterpartyrsk|1 year ago|reply
Uh, I'm surprised. How many people actually love thunderbird? And to the extend it justified the development.
[+] [-] promiseofbeans|1 year ago|reply
[+] [-] ForHackernews|1 year ago|reply
I love Thunderbird and give them money every month. Name another good open source mail client.
[+] [-] wolverine876|1 year ago|reply
[+] [-] vedmed|1 year ago|reply
That said, loving a software requires a paradigm shift for me. I can't fathom loving something that is not alive. I do enjoy it, however.
[+] [-] DrewRWx|1 year ago|reply