5.7.3 Authentication unsuccessful [CH2PR05CA0066.namprd05.prod.outlook.com]: Page 2

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

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

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.

JuVDC

Yeah I saw that... but I can't believe the solution would be to create a new mailbox... our whole support system and communications are organized around this existing mailbox...

Has anyone else solved it through the new mailbox creation?

KevinTheJedi

JuVDC

Just had a call with another customer and their SMTP was throwing same error. They deleted the email and recreated it and it worked afterwards. So definitely seems related to existing accounts. MS really needs to fix this issue.

Cheers.

jeremyCorn123

I am having the same issue with a particular email on our account. Does anyone else also have multiple domains where the username and primary email address have different domains?

KevinTheJedi

ait1

I believe they mean creating a new account (mailbox). I'm basing this off their comment above:

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

Cheers.

ait1

Hi, I have the same issue with 5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant. Visit https://aka.ms/smtp_auth_disabled for more information. [BLAPR03CA0095.namprd03.prod.outlook.com. Even though I recreated the mailbox, it still has the same issue. And I use a new mailbox to signup on the ostickte, it still has the same issue with Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant. Anyone finds the solution?

KevinTheJedi

ait1

Did you enable Authenticated SMTP permission for the User in the Exchange Admin Center? You should contact your O365 admin and have them enable it for you.

Cheers.

ait1

KevinTheJedi you are right, we forgot to enable the SMTP Authentication on Godaddy site. Thank you.

« Previous Page