475744 - No IMAP-connection with Option "TLS" but with "try TLS" (and does(!) TLS)

Status: VERIFIED DUPLICATE of bug 470067

(Thunderbird :: Preferences, defect)

Description

[hans.moser]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.4) Gecko/20030624
Build Identifier: Thunderbird 3 Beta 1

There is a working Cyrus IMAPd with a self build ca and certificate (it is a "one for all" *.domain.tld cert).
It uses TLS and shared secret auth.
This works fine with TB 1.5 and 2.0:
On first connection TB presents the cert to accept it. Works!

TB3B1 with "TLS" on tries to connect, but can't.
If i change settings to "try TLS" (I only have the german version here), it does work - with TLS! - I can see that on the IMAP server.
The cert will be stored in cert manager.

When I change back to "TLS" it does not work again.

It is the same with a new and a migrated profile. 
The same profile works with TB2.

Reproducible: Always

Steps to Reproduce:
1. IMAP-Server with TLS (it may depend on the cert)
2. Activate "TLS"
3. Connect
4. Change to "try TLS"
5. Connect
6. Change back to "TLS"
7. Connect
Actual Results:  
"imaps TLS negotiation failed"

Expected Results:  
"login: xxxxxx [10.49.9.74] username CRAM-MD5+TLS User logged in"

"Does not work"-Log

Jan 27 17:51:14 rzhs153 imaps[17699]: accepted connection
Jan 27 17:51:14 rzhs153 master[21836]: about to exec /usr/lib/cyrus-imapd/imapd
Jan 27 17:51:14 rzhs153 imaps[21836]: executed
Jan 27 17:51:18 rzhs153 imaps[21836]: accepted connection
Jan 27 17:51:18 rzhs153 master[21837]: about to exec /usr/lib/cyrus-imapd/imapd
Jan 27 17:51:18 rzhs153 imaps[21837]: executed
Jan 27 17:52:11 rzhs153 master[17687]: process 20446 exited, status 0
Jan 27 17:52:55 rzhs153 imaps[17699]: imaps TLS negotiation failed: xxxxxx [10.49.9.74]
Jan 27 17:52:55 rzhs153 imaps[17699]: Fatal error: tls_start_servertls() failed


"Does work"-Log

Jan 27 18:01:06 rzhs153 imap[22012]: accepted connection
Jan 27 18:01:06 rzhs153 master[22029]: about to exec /usr/lib/cyrus-imapd/imapd
Jan 27 18:01:06 rzhs153 imap[22029]: executed
Jan 27 18:01:06 rzhs153 imap[22012]: starttls: TLSv1 with cipher AES256-SHA (256
/256 bits reused) no authentication
Jan 27 18:01:06 rzhs153 imap[22012]: ptload(): fetched cache record (mark 123307
5027, current 1233075666, limit 1233064866)
Jan 27 18:01:06 rzhs153 imap[22012]: ptload(): fetched cache record (mark 123307
4272, current 1233075666, limit 1233064866)
Jan 27 18:01:06 rzhs153 imap[22012]: ptload(): fetched cache record (mark 123307
5027, current 1233075666, limit 1233064866)
Jan 27 18:01:06 rzhs153 imap[22012]: login: xxxxxx [10.49.9.74] tparker CRAM-MD5+TLS User logged in

Comment 1

[Mark Banner (:standard8)]

There is a know issue with beta 1 where the port is set up wrong. This is already fixed in nightly builds.

Comment 2

[Tyler Downer [He/Him]]

v.