Oauth connection for inbound emails!

Trying to configure oauth for inbound emails! But following issues are being faced!

Mon Dec 26 16:55:47 2022 [47891][1][FATAL] Using imap handler class: Imap2Handler
Mon Dec 26 16:55:48 2022 [47891][1][FATAL] An Imap error detected: "IMAP open error: Can not authenticate to IMAP server: A0001 NO AUTHENTICATE failed."
Mon Dec 26 16:55:48 2022 [47891][1][FATAL] An Imap error detected: "IMAP open error | debug data"
Mon Dec 26 16:55:48 2022 [47891][1][FATAL] An Imap error detected: "ImapHandler:open: {outlook.office365.com:993\/imap\/ssl}"
Mon Dec 26 16:55:48 2022 [47891][1][FATAL] An Imap error detected: "ImapHandler:open: admin"
Mon Dec 26 16:55:48 2022 [47891][1][FATAL] An Imap error detected: "ImapHandler:open: password is empty: no"
Mon Dec 26 16:55:48 2022 [47891][1][FATAL] An Imap error detected: "ImapHandler:open: 512"
Mon Dec 26 16:55:48 2022 [47891][1][FATAL] An Imap error detected: "IMAP open error | debug data end "

As I click on the monitored folders, the following screen pops up:

Hello,
Got the same error message even though External provider is ok and personnal oauth connexion is ok.
Thank you for admin

The username must be the email address you used to login in the outlook account! Try it and then let me know!

Also following permission were given in the azure account :

I have the same issue.
The username is the email used to log into Office365. Permissions are set correctly in Azure.

Did someone get this resolved, also have the same issue with External Provider and Connection work but getting “Login and Password incorrect” using OAuth, Imap 993 with the correct user on Azure

I am having the exact same issue. I was able to get one server working using the exact same procedure (Ubuntu 20) - my sandbox instance, but on production applying the same procedure I keep getting the invalid password.

Any assistance greatly appreciated. My logs show the same info as above!

2 Likes