unable to connect to smtp server because of invalid credentials

[balam@joskos.com]

Case #06069719
I have issue in Email Alert notification setup.

I have the similar issue:
The Email notification for alerts were working fine but all of sudden we lost receiving alerts.

When I set the notification settings and test I get an error message as "Unable to connect to SMTP server because of invalid credentials or connection settings".
The setting is:
SMTP Server is O365: smtp.office365.com
Port: 587
Connect using: SSL

*The account used is valid as I am able to login and send email with no issues.
*Port: 25, 587 is not blocked. I am in process of unblocking 465 which I would do shortly. However as per my understanding with Port 25, 587 it should work fine but its not.

On top of it, when I try to save the settings and apply, I get an error message eventually 'Failed to Register new route'.

[Mildur]

Hi Balakrishnan

Welcome to the forum.
I would go with one of those two options:

- update to V12 and use Microsoft 365 OAuth 2.0 authentication instead of SMTP.

- check if your SMTP account is allowed to send mail per SMTPAUTH. Microsoft may have disabled it for your Exchange Online user: https://learn.microsoft.com/en-us/excha ... submission

Best,
Fabian

[Symjett]

Hi,

I have the same error but I updated to version 12 and made sure that SMTPAUTH was enabled, but it still doesn't work.

What else could it be that causes this error message? MFA is disabled aswell and firewall ports are open so it should work.

best regards, Simon

[taston]

Hi, experiencing the same issue having just updraded from v11 to v12. I was wondering if you were able to fix this for SMTP or if you had to configure Microsoft 365 OAuth 2.0 authentication? Cheers

[DanTot]

Hi,

We also see this error appear on some clients with and without Hyper-V.
Do you have this problem on clients without Veeam KB4420 installed?

Recently our SMTP provider changed name to the relay, and we get this error when we try to update the name: same email, same password, it always worked.

[Mildur]

Hi Dan

Do you have an active support case for this issue? Please share the number with me.

Just to let you know, our newest release is v12.1 (12.1.0.2131). Your shared kb article references to our v12.0 builds.
https://www.veeam.com/kb2680

Best,
Fabian