User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; Maxthon) Build Identifier: version 1.0.2 (20050317) Hangs up while browsing folders through 3 IMAP accounts. I have 3 IMAP accounts, if browsing folders fast on each account - Thunderbird HANGS with "Connecting to mail.domain.com ... " in the status bar. Tried on 2 Computers at least. 2 IMAP Accounts are from the same server. And recentely I found how to fix it. On every account's properties in the Server Settings -> Advanced -> Maximum number of server connections to cache > set it to 1. Reproducible: Always Steps to Reproduce: 1. Switch to Account #1 - INBOX 2. Switch to Account #2 - INBOX 3. Switch to Account #3 - INBOX Actual Results: Hangs with the message in the status bar: "Connecting to mail.domain.com..." Expected Results: Update IMAP folder
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.