5.7.3 Authentication unsuccessful [CH2PR05CA0066.namprd05.prod.outlook.com]

DieterDeleter

Hi All,

I'm working on setting up OAuth IMAP/SMTP via Microsoft Office365 with OSTv1.17.

I am able to get each of the IMAP and SMTP sections of the OAuth config to receive tokens, but when enabling and saving the entire email config, it returns 5.7.3 Authentication unsuccessful [CH2PR05CA0066.namprd05.prod.outlook.com].

I'm not entirely sure where to debug this. What might cause it to authenticate successfully individually for IMAP and SMTP, but fail when saving as a whole when both tokens are received and valid?

KevinTheJedi

DieterDeleter

Sounds like you either didn't add the API Permissions for smtp in azure portal app registration or you need to contact microsoft for further assistance.

Cheers.

DieterDeleter

Thanks, I've definitely got the SMTP.Send in the my App Registration. I'll follow up with Microsoft, but in the meantime, can you clarify how to view OST logs for OAuth requests?

KevinTheJedi

DieterDeleter

You don’t lol you would need to view the logs on Microsoft’s end. Any errors should be logged in system logs of osticket. Other than that there are no connection logs or anything.

Cheers.

ElbowNi

I'm in the same boat, I can now receive but can't send with exactly the same error message. I too have the api with SMTP enabled?
MS Azure setup

osTicket error:

KevinTheJedi

ElbowNi

Do you have a self-signed certificate by chance?

Cheers.

ElbowNi

KevinTheJedi No mate, proper *.omgplc.com
Common Name (CN) Go Daddy Secure Certificate Authority - G2
Organisation (O) GoDaddy.com, Inc.
Organisational Unit (OU) http://certs.godaddy.com/repository/

KevinTheJedi

ElbowNi

Then contact Microsoft for further assistance.

Cheers.

abone

Hi,
trying to update to OAuth authentication.
I managed to add Remote Mailbox successfully, but SMTP is a pain

just want to confirm the same error.

ramrajone

abone
Take a look at this post, it may help out
https://howtohelpdesk.com/how-to-setup-oauth-on-osticket-using-microsoft-365/

northernnoel

I've been having a similar issue which I think is an MS one. Has anyone had any luck from their support? We've got multiple email addresses, the first one added fine and I'm now adding the second one. When adding the second one it doesn't give me the tick box when granting permissions for "Consent on behalf of your organisation". I've checked through the permissions and it's been added as an application administrator. Oauth actually completes its connection successfully, it's just when I click save on SMTP it fails. If I turn off SMTP then it saves fine and emails come in (it just can't reply).

@KevinTheJedi I don't know how you haven't lost the will to live with auth. If only MS hadn't turned off basic auth life would be much simpler 😆

KevinTheJedi

northernnoel

You can also try setting SMTP to use OAuth2 instead of same as remote mailbox, reconfigure, get a token, and retry. If that doesn’t work then you need to contact MS to see why it’s not working.

You could also try re-enabling Legacy SMTP and use username + password until you can figure out what’s happening.

Cheers.

northernnoel

I got it to work finally, it seemed to be tied to that particular mailbox. Deleted it from O365, created a new one, re-assigned the permissions and it connected first time. The only difference I could see was that this one was created before I looked after it and it was Azure synced. There's no need for it to have a local account so deleted all of that and set one up purely as cloud.

AgilitasLtd-BE

I have the same issue

latest osTicket on Ubuntu 18. Remote Mailbox with OAuth2 - Microsoft, secret, redirect URL, etc, all looks okay, but the Outgoing SMTP dialog working. It errors with "5.7.3 Authentication unsuccessful [LO2P123CA0057.GBRP123.PROD.OUTLOOK.COM]"

Hostname: smtp.office365.com
Port: 587
Authentication: OAuth2- Microsoft (or same as Remote Mailbox) which is okay

Azure AD has App Registration, redirect URL, secret, and so on, which is why the OAuth2 is okay for remote mailbox.
Azure AD API permissions also has the SMTP.Send delegated and Mail.ReadWrite delegated, and so on.

Microsoft 365 admin center -> Users -> Active users, the mailbox/user, Mail -> Manage email apps, has "Authenticated SMTP" ticked. Tried with and without tick. Still no luck. Leaving it ticked.

I originally tried using the host of [ourcompany].onmicrosoft.com, but that failed with PHP get_file_contents() returns "no address associated with hostname", so realised that was no good as it didn't ping/resolve. Checking Microsoft 365 admin center shows no MX records either for that, so tried one of the other domains, which has MX record, and then it just says Could not open socket, connection timed out. Tried with ssl:// and tls:// and various combinations of. Still no luck.
So switched and tried outlook.office365.com and smtp.office365.com for host. They resolve, but now get authentication unsuccessful as per
"5.7.3 Authentication unsuccessful [LO4P123CA0610.GBRP123.PROD.OUTLOOK.COM]"

I think it's due to smtp.office365.com being the generic 365 mailbox, but we have Microsoft 365 Business Standard, hence in other places it refers to [ourcompany].onmicrosoft.com

Wondering about creating a new mailbox as per norternnoel above, with a new email/mailbox. Luckily have a spare licensed mailbox to use.

AgilitasLtd-BE

OH! Solved. Just as norternnoel above said, creating a new email/mailbox fixed things!

So, for info, created a new active user in Microsoft/Office 365,
https://admin.microsoft.com/Adminportal/Home?source=applauncher#/users
Picked the new user, clicked on Mail on the flyout, Manage email apps, tick the Authenticated SMTP.
So now have a new mailbox. Logged into it with office online to make sure the mailbox is working.
Then tried again. Bingo, it worked.

The important things here were

fresh mailbox
Hostname for the SMTP is "smtp.office365.com" (and not the same hostname on the remote mailbox screen, this needs to be the IMAP hostname "outlook.office365.com")
SMTP Auth tick enabled for the mailbox user
correct Redirect URL in Azure which allows the reply to come back in and hit osTicket.
Azure AD application, permissions, etc as per all the online instructions.

But if SMTP thing refuses to work, then FRESH MAILBOX solved for me.

Now time to test things out using my new mailbox, which to be honest is probably what's needed anyway while we still have Spiceworks working for live issues on our main helpdesk@ email!!

EDIT: Re needing Hostname for IMAP to be outlook.office365.com

jiggs

Have you input SMTP:emailaddress@domain.com into the attribute editor or asdi edit for the proxyaddress? This would be on the DC.

KevinTheJedi

AgilitasLtd-BE

You shouldn't have to use smtp.office365.com as the host name. Both outlook.office365.com and smtp.office365.com resolve to the same servers.

Cheers.

ait1

AgilitasLtd-BE fresh mailbox

What is that mean for the "fresh mailbox"? Thank you

AgilitasLtd-BE

KevinTheJedi
Thanks. I just went with what I found in the Microsoft Info
Go to https://outlook.office.com/mail/
Then click the COG in top right, then "View all Outlook settings" link at the bottom, then "Email" → "Sync email" settings.
This showed me different settings for me, and when I ping them, I get different IP's.
It maybe they're clustered and it doesn't really matter, but thanks anyway. Lots of different answers out there and a lot of head bashing trying to get things working, and fortunately helpful people here.

JuVDC

Hey we're still encountering the same issue 🙁
Has anyone else solved this?

KevinTheJedi

JuVDC

Someone mentioned they had to create an entirely new email account for this to work. Seems related to that specific email account.

Cheers.