Closed
Bug 1411789
Opened 8 years ago
Closed 8 years ago
52.4.0 IMAP TLS stopped working with Dovecot "imap-login: Error: SSL: Stacked error: error:14094414:SSL routines:ssl3_read_bytes:sslv3 alert certificate revoked: SSL alert number 44"
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1359179
People
(Reporter: m, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36
Steps to reproduce:
Send message using IMAP with TLS on a Mac (OS X 10.12.6).
Actual results:
I get this message in Thunderbird:
There was an error saving the message to Sent. Retry?
I get this message on my server (Dovecot 2.2.22 (fe789d2))
Oct 25 21:42:34 tombstone dovecot: imap-login: Error: SSL: Stacked error: error:14094414:SSL routines:ssl3_read_bytes:sslv3 alert certificate revoked: SSL alert number 44
I can successfully copy messages to my Sent folder using other MUA (iPhone Mail, for example)
Expected results:
IMAP should work, both sending and receiving.
Comment 1•8 years ago
|
||
You are looking at bug 1359179.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Summary: 52.4.0 (64-bit) IMAP TLS stopped working with Dovecot → 52.4.0 IMAP TLS stopped working with Dovecot "imap-login: Error: SSL: Stacked error: error:14094414:SSL routines:ssl3_read_bytes:sslv3 alert certificate revoked: SSL alert number 44"
Hi Wayne,
I read over bug 1359179. I respect that Bugzilla is NOT a support forum, and I don't think I'm using it as such.
Thunderbird was working perfectly for me with my personal mail server until I upgraded Thunderbird to 52.4.0. I just now downgraded to 45.8.0 and IMAP with TLS works again.
I'd love to see what I think is a legitimate bug resolved because I really like using Thunderbird. I'm happy to help with troubleshooting.
Best,
Michael
Comment 3•8 years ago
|
||
Could this explain it?
http://forums.mozillazine.org/viewtopic.php?f=39&t=3030521
You need to log in
before you can comment on or make changes to this bug.
Description
•