Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Thunderbird 102.4.1 on Windows no longer connects IMAP TLS

  • 1 reply
  • 0 have this problem
  • 13 views
  • Last reply by mikko5

more options

Windows version of Thunderbird is no longer connecting to my IMAP server using TLS.

There is just a dot going back and forth on the inbox tab. I can view the old message, I've set it up to keep a copy, the UI seems to otherwise work, but Inbox just does not seem to connect. There is no error, nothing. Status bar says <email>: Connected to <mail.fqdn>...

I'm using a self signed CA, that I have imported into the certificate manger to identify web sites and mail users. CN is set to the FQDN, thought there are other field in the subject too.

On Arch Linux, the same Thunderbird version works just fine. Also, Android GMail is able to connect just fine. The server seems to work just fine.

Windows version of Thunderbird is no longer connecting to my IMAP server using TLS. There is just a dot going back and forth on the inbox tab. I can view the old message, I've set it up to keep a copy, the UI seems to otherwise work, but Inbox just does not seem to connect. There is no error, nothing. Status bar says <email>: Connected to <mail.fqdn>... I'm using a self signed CA, that I have imported into the certificate manger to identify web sites and mail users. CN is set to the FQDN, thought there are other field in the subject too. On Arch Linux, the same Thunderbird version works just fine. Also, Android GMail is able to connect just fine. The server seems to work just fine.

Chosen solution

Trying to send mail using TLS produced an error message that the site does not match the certificate.

The issue was fixed by adding Subject Alternative Name to the certificate.

Read this answer in context 👍 0

All Replies (1)

more options

Chosen Solution

Trying to send mail using TLS produced an error message that the site does not match the certificate.

The issue was fixed by adding Subject Alternative Name to the certificate.