Closed Bug 1679590 Opened 5 years ago Closed 5 years ago

Thunderbird 78.5.0 does not record unread emails for all folders (randomly some)

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86_64
macOS
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: gregorytarsy, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.1 Safari/605.1.15

Steps to reproduce:

OPEN THUNDERBIRD OR VIEW ALREADY OPENED THUNDERBIRD

Actual results:

MOST FOLDERS DO NOT DISPLAY UNREAD COUNT, INCLUDING INBOX. AN APPARENTLY RANDOM SELECTION OF A FEW FOLDERS DO DISPLAY UNREAD COUNT

Expected results:

ALL FOLDERS WITH UNREAD EMAILS SHOULD DISPLAY UNREAD COUNT IN THE UNREAD COLUMN.

I'm not on Big Sur, but for clarification you added the “Unread” column using “Select Columns to display” to the Folder pane?

All of my folders have the unread message count next to the folder like Inbox (23), Newegg (3) without that column in the Folder pane.

Component: Untriaged → Folder and Message Lists
Flags: needinfo?(gregorytarsy)
OS: Unspecified → macOS
Hardware: Unspecified → x86_64

Yes, I have added the Unread column using the small grid look selector for "unread", Total", "Size" as I have done for many years.
Ah! I see that if I unselect "Unread" in the column display selector then I see the counts in parentheses as you indicate. That solves the problem, although it seems to be new behavior, especially the random nature of showing some unread counts when using the Unread column. If that's the intended behavior then it should be documented and/or the Unread column removed from the display selector, seems to me. Thanks for your response!

Flags: needinfo?(gregorytarsy)
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Summary: Thunderbird 78.5.0 does not record unread emails for all folders (randomly some) on Big Sur → Thunderbird 78.5.0 does not record unread emails for all folders (randomly some)
You need to log in before you can comment on or make changes to this bug.