It's also possible that the TLS alert sent by Thundebird has recently changed and we were not signalized that re-import of the root certificate was needed. We are currently investigating if this is what happened. According to the code it would happen if Windows prevented us from accessing certificate keys.
Customers suffer.ġ, In order for SSL filtering to work, the ESET root certificate must be imported in the Thunderbird's trusted root CA certificate store in order for the mail client to trust the communication encrypted with ESET's private key.Ģ, The ESET root certificate is imported after installation provided that TB is not running or after a reboot after TB sends a TLS alert in case the certificate is unknown or expired.ģ, After the recent update of the Internet protection module the root certificate was most likely re-generated. Don't you try that in your labs ?Īlways the same : developers are disconnected with the real world. Fortunatelly, we have an OUTSTANDING support from MGK in Luxembourg, but why we - and them - have to deal with that is beyond my understanding. I can't believe this problem occurs again and that questions about us keeping on proposing this product.
It is not the first time we have that kind of issue with Nod32 and client mails, and it is VERY bothering : since yesterday, we have received many requests for help from desperate customers. I can confirm the problem between Nod32 and Thunderbird 78 : disabling the SSL/TLS filtering solve the issue.
0 kommentar(er)
