Unable to configure email with OAuth2

jnavia

Hey all,

Try as I might, I cannot get emails working. I've managed to get the token working:

Then:

However, no messages are ever fetched. And when I try to send an email from the Test Outgoing Email window, I get:

And in the logs:

I've tried everything under the sun (checked ports, changed API private key multiple times, updated to v1.17.5 from 17.2, re-installed the whole thing) and nothing seems to get it working.

Are there any other logs I can look so maybe I can confirm what the issue is EXACTLY? I don't think the "System Logs" could be more vague.

KevinTheJedi

jnavia

SMTP information is incorrect. Hostname is smtp.office365.com and Port Number is 587. You can see this from the O365 documentation here:

https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365#how-to-set-up-smtp-auth-client-submission

Cheers.

jnavia

KevinTheJedi

Thanks for the quick reply Kevin.

While I got a green banner with the above settings (sorry for missing that part) I get the following when trying to enable Email Fetching :

And outgoing still gives an error:

KevinTheJedi

jnavia

IMAP information is incorrect. Host name is outlook.office365.com and Port Number is 993. You can see this from the Outlook documentation here:

https://support.microsoft.com/en-us/office/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040?redirectSourcePath=%252farticle%252fpop-and-imap-email-settings-for-outlook-8361e398-8af4-4e97-b147-6c6c4ac95353

Cheers.

jnavia

KevinTheJedi

Sorry for confusing both protocols.
Issue still persists. It's only when I toggle Email Fetching

And still the same in SMTP:

KevinTheJedi

jnavia

Is this a real email with a licensed user account or simply a shared mailbox/resource email?

Cheers.

jnavia

KevinTheJedi

It's a real email configured on our O365 environment. I set up the API Key in Azure AD using that account as well.
The account also has all the permissions it needs as far as I'm concerned.

KevinTheJedi

jnavia

Then it sounds like the app registration wasn’t setup correctly, or the plugin information is incorrect, or both.

Cheers.

KevinTheJedi

jnavia

Here is the documentation for O365 OAuth2 Email Authorization:

https://docs.osticket.com/en/latest/OAuth2/Microsoft%20Authorization%20Guide.html

Cheers.

jnavia

KevinTheJedi

Hey Kevin,

I've followed those instructions to the tee, including setting up SSL on the Apache2 server since the Redirect URI HAS to be https://

I even went ahead and created a new client secret, and double checked all endpoints.

The issue persists. Are there any other logs I can check in the webserver itself?

jnavia

It just drives me nuts that everything says A-OK until the moment I try to set up outgoing emails. And nothing indicates why this is happening.

KevinTheJedi

jnavia

You didn’t provide admin consent for the API Permissions within the app. You need to delete the token, provide admin consent, then get a new token, and retest.

Cheers.

jnavia

Well I feel quite dumb now...

Thanks for your help and patience Kevin! Really appreciate it.

KevinTheJedi

jnavia

Don’t feel that way. A lot of people miss this step. Microsoft is ass when it comes to this stuff. The permissions clearly say they don’t require admin consent but as you’ve just learned they do require admin consent. No idea why they say they aren’t required when they are required so that’s definitely on them; not you!

Cheers.

nt8x

jnavia did you fixed it ?
I've problem same you. still not fix

jnavia

KevinTheJedi

Microsoft is ass

Tempted to make that the Best Answer of the thread.

jnavia

nt8x
I did fix it. Read the selected Best Answer .

I had to log in with an administrator account for my company's Azure platform / Entra and click on the Grant Admin Consent

Notice that now it has the green marks saying Granted for on the status column. The screenshot above doesn't have that, which is why Kevin said:

You didn’t provide admin consent for the API Permissions within the app.

If that doesn't fix it for you then you have a different issue.