KevinTheJedi,

We are a custom domain with Office365. I'm double checking the modifications and the settings I have but I am still getting the V2 api is depricated.

If you could provide exactly what settings should be in place in the Idp tab, that might be where I'm having trouble.

Thanks!

KevintheJedi,

Correction. I went back and checked the basics, the database changes did not save and it was still using the PHAR. I can confirm this is working as expected.

Thank you very much for your efforts!!!

Does anyone have a shared mailbox they can test with? I want to see what all is remaining. I know personal email accounts are not working but I can't even confirm if they were ever working before. So if someone has had an @outlook.com email working previously with OAuth2 and IMAP/SMTP but now can't let me know.

Hi,

We applied the patch you provided for our IMAP remote mailbox. It works for our case (business account).

Thanks for the reactivity !

Hi, I am also having the same issue, can someone advise the exact changes that need to be made to resolve this issue?

I have read through this thread but i'm unsure of the exact fix.

TIA

    Will the fix be included in version 1.18.2 and when will this version be released?

      Tinnitus

      I guess you didn't read this thread at all; i've already covered what you are asking. Also, why would it be included in the core code when the changes are with the plugin only?

      Anyways, new build of plugin will be released once changes are finalized. We still have to work out shared mailboxes/aliases.

      Cheers.

        So... scratch everything I said for personal accounts; I think I have succumbed to my own stupidity here... Idk how the hell I overlooked the most simple setting. Yes, Personal Accounts do in-fact work just fine. All you need to do is apply the changes to the plugin as described above but CREATE YOUR APP REGISTRATION TO ALLOW PERSONAL ACCOUNTS 🤦‍♂️

        So the only thing remaining is shared mailboxes/aliases. We should have a working plugin for that next week as it requires a bit of changes and testing.

          KevinTheJedi
          Hello Kevin, did you need people to test shared mailboxes? I use shared mailboxes and they work normally, no changes there.

            KevinTheJedi Just to add another confirmation, this modification worked for me when using a shared mailbox. However, I did log into the shared mailbox directly (yes, I know - not best practice but it works), so I'm not sure this provides any additional information for confirmation of a fix 😐️

            Thanks for the modification! I suspect a lot of people will have expired client secrets around now given it's just over 2 years since the plugin was released!

                RBGE

                Nah, that’s the (insert nerd voice) “you’re not supposed to do it that way as you are voiding license by doing so” way. Trust me, MS “pros” (purists) got mad at me for recommending that. 🙄

                Anyways, we have an idea of how to accomplish this so I’ll post a new build here for peeps to test the shared mailboxes/aliases using a service account or an account that has full read/write permissions to the mailbox to fully confirm it’s working again.

                Cheers.

                    Just to confirm that the posted fix works for me, once I remembered the 1 to 0 in the DB table to tell it to not use phar!

                    The fix worked for us as well.... until this morning. Now we are getting an invalid_client error.

                      Ill look around. Been working fine for years and just stopped this morning. Sus