I can confirm this modification has allowed me to configure M365 on business email.
It has successfully fetched the backlog emails and sent all the auto reponses.
Is this safe to keep using long term or a temporary fix/hack?
MS OAuth2 Error: The API version 'V2' has been depreciated.
Keep using it until the changes are officially made to the plugin and a new build is released.
Cheers.
That basically confirms that personal accounts still have something majorly wrong with them as the same steps simply do not work. Unless someone else with a personal account can test and see as maybe it’s an issue with my account only.
I presume I can add another test account. Just to see if it will work. Got an @outlook.com account, but do you need be a developer to add app registration? It doesn't allow me.
Interesting, mine lets me and it’s a fairly new account. So the way it’s looking so far it appears they are killing or have killed imap and smtp for personal accounts…that’s messed up.
Cheers.
- Edited
I can't imagine they are blocking it, perhaps some update went wrong. Doesn't 3rd party email clients use this same method? Something like emClient would still be able to send/receive via SMTP and IMAP surely.
What happens if you try make a NEW app reg? Does it let you?
Do you have a free Azure account? ChatGPT seems to think that is how you can make new App Reg's.
- Edited
Yea created two new ones today.
Yea but most these days switched to API based calls to retrieve mail instead of using the IMAP/POP3 protocols; but even then thinking about it you would still need oauth2 so that doesn’t matter. Regardless, as I said the exact same steps taken to get it working for business does not work for personal (I’ve tried).
I have free and paid (family) plan ones.
Cheers.
KevinTheJedi I'm confirming your proposed change does work with a businessaccount.
jerer This worked.. Support portal is back to normal. Hope OS ticket team will officially attend to this issue and fix. As this is a workaround.
KevinTheJedi Yes. Everything is working as expected after the php changes you provided.
KevinTheJedi
Hi, It's work for me too. Thank you ! You save my day !
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, the fix worked for me, thank you for the assistance.
- Edited
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?
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.