-
- Influencer
- Posts: 11
- Liked: 3 times
- Joined: May 26, 2020 1:04 pm
- Contact:
Re: Configuration backup notification seems to use a different SMTP TLS validation check from other notification
After solving this problem a few months ago by re-creating the Veeam Self-Signed Certificate the problem just reappeared for me. It also exists in Veeam One, so I am not receiving monitoring emails as well. I tried updating to the latest patch, that @Mildur just referred to, but unfortunately the problem persists.
-
- Service Provider
- Posts: 8
- Liked: 5 times
- Joined: Feb 11, 2020 12:15 pm
- Full Name: Luca Marohn
- Contact:
Re: Configuration backup notification seems to use a different SMTP TLS validation check from other notification
Can confirm, the KB4420 does resolve issues on servers where VBR loops endlessly on checking the cert.
-
- Influencer
- Posts: 11
- Liked: 2 times
- Joined: May 23, 2014 9:37 am
- Full Name: Nestea1
Re: Configuration backup notification seems to use a different SMTP TLS validation check from other notification
Can also confirm, endless Loop does not appear after newest Patch.
But Certificate (from Google SMTP) still happens after times.
But Certificate (from Google SMTP) still happens after times.
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Configuration backup notification seems to use a different SMTP TLS validation check from other notification
Hi guys
It seems that we fixed one part of the issue. But the main cause requires more changes which are planned to be delivered with V12a.
Let me check again in our system.
Best,
Fabian
It seems that we fixed one part of the issue. But the main cause requires more changes which are planned to be delivered with V12a.
Let me check again in our system.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Influencer
- Posts: 12
- Liked: never
- Joined: Aug 07, 2020 6:25 pm
- Contact:
Re: Configuration backup notification seems to use a different SMTP TLS validation check from other notification
Applied the mentioned update.
Mail was working after "trusting" the certificate before that.
Then, the Lets Encrypt certificate got renewed.
Veeam now fails again to send mails.
Go to SMTP Settings, re-apply, got prompted again for Not Trusted certificate being installed on the remote Postfix server...
This is on Veeam B&R 12.0.0.1420 P20230718.
Mail was working after "trusting" the certificate before that.
Then, the Lets Encrypt certificate got renewed.
Veeam now fails again to send mails.
Go to SMTP Settings, re-apply, got prompted again for Not Trusted certificate being installed on the remote Postfix server...
This is on Veeam B&R 12.0.0.1420 P20230718.
-
- Influencer
- Posts: 11
- Liked: 3 times
- Joined: May 26, 2020 1:04 pm
- Contact:
Re: Configuration backup notification seems to use a different SMTP TLS validation check from other notification
@ Mildur / Fabian
The problem also exists in Veeam ONE, btw. So maybe you can share your progress on that issue with the other team.
The problem also exists in Veeam ONE, btw. So maybe you can share your progress on that issue with the other team.
-
- Influencer
- Posts: 11
- Liked: 2 times
- Joined: May 23, 2014 9:37 am
- Full Name: Nestea1
Re: Configuration backup notification seems to use a different SMTP TLS validation check from other notification
Some Updates with Version Veeam B&R 12.1?
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Configuration backup notification seems to use a different SMTP TLS validation check from other notification
Hi Nestea1
The SMTP module was reworked for v12.1. It also solves the SMTP thumbprint issue from this topic.
All Bug IDs regarding these issues are marked as fixed with v12.1.
Please update to v12.1. If you still face the same issue, open a support and let me know the case number.
Best,
Fabian
The SMTP module was reworked for v12.1. It also solves the SMTP thumbprint issue from this topic.
All Bug IDs regarding these issues are marked as fixed with v12.1.
Please update to v12.1. If you still face the same issue, open a support and let me know the case number.
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: masahiro.takahashi, Semrush [Bot] and 59 guests