289407 - Courier-IMAP: New mail headers of sub-folder are not displayed after checking for new mail

Status: RESOLVED WORKSFORME

(Thunderbird :: General, defect)

Description

[Rolf]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: 

When a subfolder is opened after Thuderbird displays that unread messages are in
this folder (After check for new mail) no new messages are displayed.
When a subfolder has been open before the problem does not appear.

Courier IMAP (debian woody) running with mailfolders.

Reproducible: Always

Steps to Reproduce:
1. Mark subfolder to check for new mail
2. Wait until new mail is found
3. Click on subfolder

Actual Results:  
Thunderbird displays that new messages are available in the subfolder
However messages are not displayed

Expected Results:  
Display new messages

Comment 1

[hansen]

Don't know if this is the issue, but I'll try anyway.

How many connections from each IP do Courier-IMAP allow? By default it's 4.
Thunderbird has default 5 connections as default.

* Adjust the connections on the server to match Thunderbird or
* Tools > Account Settings > [account] > Server Settings > Advanced > Maximum
number of server connections to cache.

I'm not having any issues.
What versions of Courier and Thunderbird are you running?

Comment 2

[Rolf]

Reducing the maximum connections from Thunderbird to the Courier server to 4 
solves the issue.

However, couldn't Thunderbird detect that the connection failed, and take 
appropiate actions? (And not just canceling the connection without any notice.)

Comment 3

[Gervase Markham [:gerv]]

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/