Bad sequence of commands SMTP setting using OAuth2 for O365

Davidleecs

I'm getting error when setting up the SMTP with OAuth2 authentication same as remote mailbox for O365 and getting error Bad sequence of commands below.

Osticket ver 1.18.2
Apache 2.4.58
MySQL 8.0.41
PHP 8.1.32
OAuth2 client plugin ver 0.6

There is no issue saving for incoming mailbox and I can see the OAuth2 Authorization token scopes below
https://outlook.office.com/IMAP.AccessAsUser.All
https://outlook.office.com/Mail.ReadWrite
https://outlook.office.com/POP.AccessAsUser.All
https://outlook.office.com/SMTP.Send
https://outlook.office.com/User.Read

Is there anyone encounter same issue and appreciate can share workaround resolution?

KevinTheJedi

Davidleecs

Please read the system requirements before upgrading/installing. You have PHP 8.1 but the minimum supported now is 8.2. Please upgrade and retest.
You’ll can’t use Mail.ReadWrite anymore so remove that scope and reauthorize the email.
Ensure Authenticated SMTP is enabled for the email in Office365. Make sure you have no policy attached that would prevent it, etc.

Cheers.

Davidleecs

KevinTheJedi

Thanks for sharing these info. I've follow your advices, updated the to latest PHP 8.4, remove Mail.ReadWrite scope and reauthorize the email but still getting same error Bad sequence of commands.

KevinTheJedi

Davidleecs

Then the only thing I can think of is your hosting provider is blocking/restricting external SMTP.

Cheers.

Davidleecs

I've verified there is no blocking from the network nor ISP provider the osticket server to external SMTP. I'm looking forward see see if anyone in this forum encountered the same issue and have any workaround to diagnose and setup the outgoing SMTP with O365.

Davidleecs

Any expertise able to share resolution to address the error of outgoing SMTP with O365?

KevinTheJedi

Davidleecs

I’ve already exhausted the options I had on my end. You just make sure there is no blocked ports, no smtp restrictions on the server, ensure the scopes are correct and updated, make sure the user in azure has the perms enabled, make sure there is no policy blocking them, etc. To me it sounds like host issues or issues with the app registration or user account. Try fully creating a new app registration and updating everything in osTicket.

Cheers.

Davidleecs

Issue has been resolved. I managed to identified the network firewall blocked the SMTP authentication request to O365 which is not shown in any firewall logs.

KevinTheJedi

Davidleecs

Aha! I knew it was something of the sorts. Glad you got it worked out!

Cheers.