KevinTheJedi I'm not this familiar with php, is it as simple to just repack the plugin instead? If so, it makes sense to me that it'd be easier to unpack, modify, and then repack the plugin instead of modifying the DB.
MS OAuth2 Error: The API version 'V2' has been depreciated.
ognalysis Sure go for it.
KevinTheJedi I was hoping you maybe had a oneliner for packing it. If not, nbd, just wanted to ask.
I've unpacked and modified the php as you indicated, however, the DB settings are already as you described (install path has no .phar, and isphar is already 0). Should I just replace the whole original plugin directory with the new unpacked one?
No, there should be a folder called auth-oauth2/ within the include/plugin/ folder if you followed my steps correctly.
Cheers.
- Edited
KevinTheJedi There is, but within that folder, it looks like the phar is already unpacked.
I went ahead and just copied the changes to the existing oauth2.php, no db modifications, and reran the token refresh. No error, and I just got the ticket generations. As far as I can immediately tell, your changes worked.
EDIT: for reference, we're on 1.17.2, using a custom domain within Exchange Online (no outlook.com or onmicrosoft.com)
After getting a token successfully can you save changes with the Remote Mailbox tab Status set to Enable?
Cheers.
Okay so from what I’m gathering it appears that @outlook.com emails must be special and are still broken however business emails and exchange online emails should be fine after the plugin changes. Let’s hope they fix personal emails otherwise they will be in hot water.
@KevinTheJedi - Same issue for me. Secret expired and adding new only allows SMTP not IMAP download.
Do you have an updated plugin or is it manual at this stage?
I'm using M365 business email.
TIA
Steve
Everything manual at this stage. Still need more confirmations the changes actually work.
Cheers.
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?
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.