User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

Try to fetch mail from POP3 account

Actual results:

Error occurs, no mails fetched.

Please tell how I can assist you in further debugging.

This is the pop3 server certificate:

Certificate:
Data:
Version: 3 (0x2)
Serial Number:
ac:fb:55:89:d9:76:f2:0e
Signature Algorithm: sha256WithRSAEncryption
Issuer: OU = POP3 server, CN = regen.heimnetz.zone, emailAddress = [email protected]
Validity
Not Before: Dec 12 17:30:09 2015 GMT
Not After : Dec 9 17:30:09 2025 GMT
Subject: OU = POP3 server, CN = regen.heimnetz.zone, emailAddress = [email protected]
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (1024 bit)
Modulus:
00:ba:fc:db:87:cf:47:c4:f7:fc:58:87:ce:55:cf:
[...]
Exponent: 65537 (0x10001)
X509v3 extensions:
Netscape Cert Type:
SSL Server
Signature Algorithm: sha256WithRSAEncryption
5b:46:c0:8a:21:c8:80:83:0e:1e:68:9a:c7:10:9d:6f:eb:6a:
[...]

Expected results:

Mails fetched.

POP3-Server (Dovecot 2.3.18) says:

dovecot[1210]: pop3-login: Disconnected: Connection closed: SSL_accept() failed: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42 (no auth attempts in 0 secs): user=<>, rip=192.168.1.10, lip=192.168.1.1, TLS handshaking: SSL_accept() failed: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42, session=<ritsojTj1MnAqAEK>

Fetching with the POP3 account with TB 91 and all versions before worked for years, after Update to TB 102 now I get this error message and it does not work anymore.

Exact version with this issue: TB 102.0.1

I have the above mentioned self signed server certificate in the TB server certificate store.

BTW would be good if failure to fetch POP3 mails would result in a user interface error message popup.
Right now, I only recognized the failure because I was missing mails.

Thanks for reporting, will make a fix soon.

Pass urlListener to Pop3Client before connecting, to receive failedSecInfo.

Pushed by [email protected]:
https://hg.mozilla.org/comm-central/rev/d89c7e2f1253
Support self-signed certificates in pop3-js. r=#thunderbird-reviewers

Comment on attachment 9284642 [details]
Bug 1778464 - Support self-signed certificates in pop3-js. r=#thunderbird-reviewers

[Approval Request Comment]
Regression caused by (bug #): bug 1707548
User impact if declined: Self signed certificates don't work with pop3-js
Testing completed (on c-c, etc.): c-c
Risk to taking this patch (and alternatives if risky): low

Will this be fixed in TB 102? With todays update to 102.0.3 the issue is still.

(In reply to Arvidt from comment #9)

Will this be fixed in TB 102? With todays update to 102.0.3 the issue is still.

Yes, we need to land the patch to 104beta first, then I will uplift to 102esr.

Comment on attachment 9284642 [details]
Bug 1778464 - Support self-signed certificates in pop3-js. r=#thunderbird-reviewers

[Approval Request Comment]
Regression caused by (bug #): bug 1707548
User impact if declined: Self signed certificates don't work with pop3-js
Testing completed (on c-c, etc.): beta
Risk to taking this patch (and alternatives if risky): low

Comment on attachment 9284642 [details]
Bug 1778464 - Support self-signed certificates in pop3-js. r=#thunderbird-reviewers

[Triage Comment]
Approved for esr102

Thunderbird 102.1.1:
https://hg.mozilla.org/releases/comm-esr102/rev/c08544b9e4c1