367801 - No automatic mail fetch retry if connection fails with PR_CONNECT_RESET_ERROR

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Marco Franzen]

User-Agent:       Mozilla/5.0 (X11; U; Linux i586; en-GB; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i586; en-GB; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1

My mail server (uw-imapd) has an expired certificate, and one for "hostname." while the server is configured in Moz as "hostname".
Up to Seamonkey 1.0.7 I got two confirmaion dialogs (one for the certificate's host name and one for its expiry) and when both given OK, a third dialog asking for the password came up. With the password given correctly, mail was retrieved.
With Seamonkey 1.1 the first two dialogs still come up, but despite giving them the OK, Seamonkey does not ask for the password and does not retrieve any mail. It silently gives up.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Actual Results:  
The mail password is not asked and no attempt to retrieve mail is made.

Expected Results:  
The password should be asked and mail should be retrieved.

Comment 1

[Kai Engert [:KaiE:]]

I wonder if this is related to bug 368126.

Could you please try to dismiss the dialogs very quickly, within 5 seconds?

Comment 2

[Marco Franzen]

Yes, then it works.

However, apart from bug 368126, there may be an additional issue here: it gives up _silently_. (At first I just thought there was no new mail.)

Would that happen too without a bad cert but with the server not responding, when the timeout fires as intended?

Comment 3

[Kai Engert [:KaiE:]]

(In reply to comment #2)
> Yes, then it works.

Good, thanks for testing. Making depent on bug 368126.


> However, apart from bug 368126, there may be an additional issue here: it gives
> up _silently_. (At first I just thought there was no new mail.)
> 
> Would that happen too without a bad cert but with the server not responding,
> when the timeout fires as intended?

Yes, you are right.

Scott, David, could the mailnews component retry to fetch mail, if it gets a PR_CONNECT_RESET_ERROR, before any data was transfered?

The HTTP engine retries on that code.

The PSM/SSL layer makes use of that error code to "signal" a failure in SSL, asking for a retry.

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to comment #2)
> Yes, then it works.
> 
> However, apart from bug 368126, there may be an additional issue here: it gives
> up _silently_. (At first I just thought there was no new mail.)
> 
> Would that happen too without a bad cert but with the server not responding,
> when the timeout fires as intended?

David, would bug 333661 help?

Comment 5

[Serge Gautherie (:sgautherie)]

Did bug 368126 fix this ?

Comment 6

[Wayne Mery (:wsmwk)]

Given at least one part of this was definitely fixed long ago, probably not worth keeping open unless someone wants to test it