566094 - Missing/incorrect unread counts or indications make filtering on incoming mail unusable.

Status: RESOLVED DUPLICATE of bug 573158

(Thunderbird :: Folder and Message Lists, defect)

Description

[Ralph Alter]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4

Problems with incorrect unread message counts and bold flagging for folders holding unread messages have been reported frequently. See e.g. 228168; lots of others. Issue is that I cannot use filters on incoming unread mail because I cannot find the unread messages to read them. If there is another way, please advise and I will use as a workaround. As is, I see no alternative to turning off all filtering on incoming mail.

Reproducible: Always

Steps to Reproduce:
1. Create deep folder/subfolder structure for messages.
2. Create filters that sort incoming unread messages to subfolders deep in the structure.
3. Get mail incoming, let filters distribute them to subfolders.
4. Observe that many folders having unread messages somewhere below show no indication either bold (on higher level folders) or even on the folder itself (in bold and should show a count). 
5. When open that folder bold and count of unread in it show up.
6. If I hadn't thought to look in the right folder I would never have known about those unread messages.

Actual Results:  
See above.

Expected Results:  
Described above.

At a minimum it should always show the existence of unread messages (via bold name is OK) in a folder or a subfolder somewhere down in the substructure. That is the minimum necessary to find all the unread messages that just arrived if they were moved automatically by the filters. Showing the count of unread at least on the folder itself is also desirable; better would be the total number of unread in all children subfolders on every ancestor folder.

Comment 1

[Janos]

My exact experience of late (has not always been the case), bug report of the same issue:
e.g. 573158. 

Please advise on workaround or provide a solution.

Thx,
Janos

Comment 2

[Ludovic Hirlimann [:Usul]]

More activity on bug 573158