1818945 - IMAP connection times out after a couple of minutes [imap-js]

Status: RESOLVED WONTFIX

(MailNews Core :: Networking: IMAP, defect)

Description

[Mark Banner (:standard8)]

STR

1. Start up Thunderbird with imap-js enabled.
2. Select a few folders across multiple accounts
3. Wait for a few minutes

Expected Results

=> Thunderbird to continue working normally.

Actual Results

=> Thunderbird presents multiple tab modal dialogs (one for each folder selected) stating: "Connection to server <hostname> timed out."

Messages for each folder are logged to the console:

mailnews.imap.3: 
error { target: TCPSocket, isTrusted: true, name: "NetworkTimeoutError", message: "Network", errorCode: 2152398862, srcElement: TCPSocket, currentTarget: TCPSocket, eventPhase: 2, bubbles: false, cancelable: false, … }
 NetworkTimeoutError Network 2152398862 ImapClient.jsm:907:18
    _onError resource:///modules/ImapClient.jsm:907

This does not occur with imap-js turned off. It does not seem to occur with the mozilla.org server, only my local ISP.

Note: if the timeout alert is acknowledged before the next error occurs, then I think I only get a single alert per account. If I don't, then I get multiple alerts.

Comment 1

[Mark Banner (:standard8)]

This could also be related to bug 1818943 if some of the capabilities handling is not being fully parsed because of the failures there.

Comment 2

[:gerard-majax]

Also hitting that, either on GMail or FastMail (I have both), with the difference I dont get any modal dialog.

Comment 3

[:gerard-majax]

(In reply to Mark Banner (:standard8) from comment #1)

This could also be related to bug 1818943 if some of the capabilities handling is not being fully parsed because of the failures there.

I'm not seeing this in my case but rather bug 1818380

Comment 4

[Magnus Melin [:mkmelin]]

Comment 1 seems likely. Probably non correct handling of unexpected/invalid responses elsewhere could also be the issue.

Comment 5

[Geoff Lankow (:darktrojan)]

The IMAP JS implementation is being removed from the tree in bug 1947955.