backup job email notifications not working consistently

[jcofin13]

Failed to send report to '<email address>'
[14.08.2024 19:45:29.302] <01> Error (3) The remote certificate is invalid according to the validation procedure. (System.Security.Authentication.AuthenticationException)


I see this randomly for config job backups as well as regular backup notifications.

I have been in and "re-setup" my smtp settings and saved them to reaccept the cert and that may or may not work for a few days. I don think this was an issue prior to 12.1. I am not sure what else to check. The email server used is not a public facing service like gmail etc. Its an internal sever.

Oddly sometimes it does allow emails through as expected.

I am out of ideas. I found a thread that talks about it maybe being related to TLS but i cant get to the article (KB2853) to confirm its related or not.
Also...the "test" email button works everytime with no issues.

What else can i be checking to get this resolved?

[david.domask]

Hi jcofin13,

Regrettably we won't be able to assist with any meaningful troubleshooting over the forums, so please open a Support Case for the issue and allow Veeam Support time to review. Please be sure to include logs from the Veeam Server on the case for Support to review. (Use the 3rd radio button and select the Veeam server from the host list in the Log Export Wizard)

Please share the case number here once opened.

Just a quick question though to confirm the behavior you're seeing -- is the certificate for the SMTP server being updated on a regular basis? And simply "Apply"-ing the Email Notification configuration resolves the issue until the next certificate swap?

[jcofin13]

Thanks. i will get a case going.

Yeah its odd. Typically if i see a job error saying it cant send the email at the end of the job i can go into the global notification settings in veeam...change away from SMTP and select say....o365......saving and then going right back into the same setting and changing it back to SMTP. This forces veeam to check the cert again which gets accepted.

That used to work but lately more and more that might only work for 1 day or it may not work at all and ill have the same error the next morning.

The cert on the server wouldn't be swapped out that frequently i wouldn't think but i can certainly check into that and try to sort out how often it is updated.
This is what has me thinking its more of a TLS issue or something with a new feature in 12.1.

I will get a ticket going and start there.