382815 - More annoying UI race issues

Status: RESOLVED WORKSFORME

(Thunderbird :: General, defect)

Description

[P Nienaber]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
Build Identifier: version 1.5.0.12 (20070509)

(see also bug 239616) If thunderbird detects an unsigned or expired cert when trying to connect to a mailserver, it pops up a little window warning the user of this fact.  If the Continue button is clicked after Thunderbird has given up on the connection attempt, Thunderbird becomes unusuable until it gives up again, instead of retrying, or being smart enough to give up right away and allow the user to invoke a retry.  This cost me the text of a very important e-mail this morning.

Reproducible: Always

Steps to Reproduce:
1.  Try to send/receive mail via SSL.
2.  Ignore the cert warning window for a while. (ex: go to the bathroom after hitting "send")
3.  Click Continue.
Actual Results:  
Thunderbird's backend just hangs for a while.  Eventually it will time out.

Expected Results:  
As the connection attempt that the warning window is for has already expired, clicking Continue should result in ANOTHER attempt OR in an IMMEDIATE error.

Comment 1

[Wayne Mery (:wsmwk)]

P Nienaber, Do you see this with version 2?

Comment 2

[Colin Dean]

I reported this bug on the IMAP timeout bug, mistaking causes.

https://bugzilla.mozilla.org/show_bug.cgi?id=409259#c1

Comment 3

[P Nienaber]

Appears to work now (2.0.0.14).  Sort of inelegant though, as it does just dump me back to the standard connecting to SMTP server failed error, which isn't -exactly- what happened (connection timed out waiting for user -- reaching the SMTP server worked fine).  Might be worth fixing that, might not, but changing status to Minor for now, as the risk of data loss is no longer present.

Comment 4

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

(In reply to comment #3)
> Appears to work now (2.0.0.14).  Sort of inelegant though, as it does just dump
> me back to the standard connecting to SMTP server failed error, which isn't
> -exactly- what happened (connection timed out waiting for user -- reaching the
> SMTP server worked fine).  Might be worth fixing that, might not, but changing
> status to Minor for now, as the risk of data loss is no longer present.
> 

Please file a separate bug for the other issue -- this bug can then be resolved WFM.

Comment 5

[P Nienaber]

Yep, still (2.0.0.17) just gives me an error now.  Filing another bug about the erroneous error text.

Comment 6

[Wayne Mery (:wsmwk)]

correct resolution