Ever since we announced our intention to disable Basic Authentication in Exchange Online we said that we would add Modern Auth (OAuth 2.0) support for the IMAP, POP and SMTP AUTH protocols.
Today,...
Updated Jun 30, 2022
Version 6.0
Blog Post
1 MIN READ
Announcing OAuth 2.0 support for IMAP and SMTP AUTH protocols in Exchange Online
Hi Decomplexity ,
Thanks for your fast reply. Unfortunately that's not good news...
Do you have any suggestions?
Can I use authorization code flow, and let the app ask the end user who owns the mailbox to give consent for access once (interactively) and keep a refresh token somewhere which can be re-used indefinitely? Keeping in mind that it's a console app that is started from the Windows task scheduler on regular intervals, and does not stay active so the token will not stay in memory?
Client credentials grant flow cannot be used with IMAP, but can I at least somehow prevent that our customer's admin has to give us consent for access to all their mailboxes, if we only need acces to one of their mailboxes?
Or any other idea besides asking our customer to put an automatic forwarding rule on their mailbox, to send them to another mailserver which we can access via IMAP (not Office 365)...?