My organisation has moved to office365 but has not enabled EWS. This make the akonadi EWS component useless to me.
On the other hand they have enabled IMAP with OAUTH2. Thunderbird support IMAP+OAUTH2 for both receiving and sending and therefore works in my use case. kmail sadely doesn't as I cannot select oauth2 with an IMAP server.
With Microsoft having started to disable all forms of basic auth for their office365 tenants, I think this bug deserves a higher importance.
Given that Office365 situation, I agree. I think it's still "wishlist" because it's a feature request, but I'll increase from "normal" to "high".
*** This bug has been confirmed by popular vote. ***
Does this commit is a good base to implement it?
It was written by @dvratil
Does someone tried https://github.com/simonrob/email-oauth2-proxy ?
I need this badly. Our IT department just changed the settings so I can no longer access my email on Office365 via IMAP. In addition, EWS is also failing since none of the user agents are supported (and there's a bug where it's impossible to override it for the first time, but this is unrelated to IMAP).
Since Microsoft now mandates the use of oauth2 for IMAP with office365, this bug is now more important than ever. It is now impossible to use KMail/Kontact with Office365 without jumping through some major hoops with proxies, etc. Many corporate organizations use office365. I'm now stuck with Thunderbird for my work email and I am not at all happy about running that CPU pig (CPU usage is pegged at well over 100% at all times).