2 ms·

I was talking about proprietary OAuth2 authentication protocol implementations in that statement. Like how the Thunderbird OAuth2 protocol for gmail is incompat

I was talking about proprietary OAuth2 authentication protocol implementations in that statement. Like how the Thunderbird OAuth2 protocol for gmail is incompatible with the one for yahoo email, and so on. Which is different from normal protocols like imap/pop3 where the implementations are compatible across companies. I was not speaking in the context of exchange but in the more general sense of new HTTPS based protocol flavors being added to Thunderbird regularly.

sir 3y ago
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 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?