323191 - Times out reading large IMAP folders (should increase timeout value!)

Status: RESOLVED WORKSFORME

(Thunderbird :: Mail Window Front End, defect)

Description

[Braden]

Thunderbird 1.5 now times out when reading large IMAP folders (e.g., 6600 messages). This worked in 1.0.7.

Comment 1

[David :Bienvenu]

try increasing the network timeout pref, tools | options | advanced | network connection timeout - make it 10000 or so...

Comment 2

[Scott MacGregor]

we might want to think about making this a bit longer David. I've gotten comments from folks in the office about this too, they keep running into the timeout. 

Comment 3

[David :Bienvenu]

yes, I guess so - we could make it two minutes. I also like the idea of letting the user change the timeout directly from the alert, or at least having a button to take them to the ui for setting the timeout.

Comment 4

[Braden]

Yes; that works. Thanks.

A longer default timeout would be nice; but making this option discoverable by putting it in the timeout dialog (with a "Retry" button) is probably the Right solution.

Comment 5

[Wayne Mery (:wsmwk)]

i frequently get problems on a folder with >3,000

Comment 6

[Wayne Mery (:wsmwk)]

David, do you see any value to morphing this to enhancement for the UI you suggest in comment 3?  Perhaps dubious unless your experience negates the lack of dupes and other open bugs which include

bug 340265 can't remove/delete large number of messages at the same time, timeout error
bug 406929 "message was sent but copying to sent folder failed" error after IMAP timeout
bug 468490 IMAP IDLE does not reconnect after a server timeout drops the connection
409259 Thunderbird timeouts of IMAP operations 


(In reply to comment #5)
> i frequently get problems on a folder with >3,000

I no longer remember the context in which I saw this - but I don't see timeout anymore (perhaps a slow vpn?).

anyways, Braden reports he doesn't see this and "I think performance issues on the server were resolved."

Comment 7

[Braden]

I haven't observed a problem like this for some time; and I'm skeptical there's enough information in this bug report for anyone to do anything useful with it.