Mailspring-Sync VS email-oauth2-proxy

I was hopeful that https://www.nylas.com/ would be the de-facto "adapter" placing a common API surface on top of the major providers and dragging them into a modern-API world. They even had an email client of their own as a proof of concept (forked by one of the original authors as https://github.com/Foundry376/Mailspring - and its reusable core https://github.com/Foundry376/Mailspring-Sync may be interesting to many here). But they've pivoted towards making their API only available behind B2B contracts and opaque pricing, and primarily used for corporate email monitoring and CRM use cases - perhaps because security and privacy considerations are nontrivial. I'm still rooting for them but it's a shadow of what it could have been.

MailSpring is either done to look at soon ... it's either very close to finalizing Bridge support or in fact done. It's not clear to me, there's a discussion in GitHub. Nice thing about MailSpring is that it has a Linux client (Postbox only has Mac and Windows).

Yeah that's what I found too.

What makes you say the protocol is different for each provider?

I maintain a proxy that transparently adds support for OAuth 2.0 support to IMAP/POP/SMTP clients (https://github.com/simonrob/email-oauth2-proxy), and for normal use it doesn’t need to know anything about which service it is connecting to. Apart from advanced features such as CCG or ROPCG which are mostly O365 only, what is different?

When it became clear many major email providers were going to require OAuth for IMAP/POP/SMTP access, I was pretty frustrated that I’d have to stop using clients/scripts that didn’t support this method.

Rather than spending lots of effort on migration, or switching clients entirely, I made a local proxy so that any IMAP (or POP/SMTP) client can be used with a “modern” email provider, regardless of whether it supports OAuth 2.0 natively: https://github.com/simonrob/email-oauth2-proxy. No need for your client to know about OAuth at all.

If you are not familiar with Email OAuth 2.0 Proxy by Simonrob, I would recommend you check it out. Star the repo or whatever you normally do. I wanted to acknowledge his repository because my work is built directly off what he maintains and creates.

https://github.com/simonrob/email-oauth2-proxy

"Just works" I run it with mbsync at the command line.

You do need a client id and some interaction with your O365 admin.

One potential solution I found is a proxy. Are you able to utilize an app password for this task?

You do still need details for an authorised client, but it’s possible to use those of one that’s already approved. See the readme section that explains this aspect: https://github.com/simonrob/email-oauth2-proxy#oauth-20-clie...

If you use this proxy of mine then any IMAP (or POP/SMTP) client can be used with a “modern” email provider, regardless of whether it supports OAuth 2.0 natively: https://github.com/simonrob/email-oauth2-proxy

maybe you can use https://github.com/simonrob/email-oauth2-proxy while you wait for official oauth2 support but I wonder why you are using another email server if you already have exchange online