Closed Bug 1665382 Opened 5 years ago Closed 5 years ago

Thunderbird 78.2.2 problems with self signed certificate

Categories

(Thunderbird :: Account Manager, defect)

x86_64
Windows 10
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1665577

People

(Reporter: tarenal.ccit, Unassigned)

Details

(Keywords: regression)

We were using Thunderbird 68.12.0 in our organization with no problem using self signed certificates for our imap (993 port) and smtp (465 port) servers.

But today, Thunderbird was automatically updated to the 78.2.2 version, and immediately after, we couldn't send neither receive emails. The message shown after trying to send an email is:
"Sending of the message failed. The certificate is not trusted because it is self-signed. The configuration related to x.x.x.x must be corrected"

Apart of this message, there is no other window requesting us to add an Exception to these certificates as it was shown in previous Thunderbird versions. Moreover, if we go to "Manage certificates" in the Tools menu, the certificate exception can't be added manually. It gives an error saying that it can't get the certificate information.

We think this might be a bug in the new version because if we go back to the 68.12.0 version, then the software request us automatically to add an Exception for the self signed certificates and after that, we can send and receive mails. We also have no problem configuring our smtp/imap servers through Outlook or Gmail.

Is there any workaround to be able to use self signed certificates with the newer 78.2.2 version of Thunderbird? Is it happening to someone else?

Thank you very much,
cctesa

Hi again,

We've captured the following error in Thunderbird 78.2.2 that may be related to the problem described above:

[Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]" nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location: "JS frame :: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync :: line 658" data: no]

The error is related to the file L10nRegistry.jsm:658:19

For imap, see bug 1590474.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Keywords: regression
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.