index shows 1 unread message but folder empty
Recently, one of my "other" mailboxes showed 1 unread message in the index, though there was nothing in the inbox at all. I checked my email server via its webmail and found that mailbox indeed empty. Today, a second "other" mailbox shows the same problem. I've tried the "repair" and "compact" functions, but nothing changes. I've tried various folder modes, but no change. I've tried "mark folder read" but no change. This is T'bird 115.5.1 (64-bit) on Windows 10. I fear that this problem will creep to include all my mailboxes. Any ideas?
Chosen solution
Stop the Presses! Today the problem is gone! It was one of those days when all the stuff deleted in the last year or so shows back up in the "Junk" and "Trash" folders and has to be deleted all over again. I'm guessing that's the fault of the mail SERVER, which has nothing to do with T'Bird. Anyway, after I re-deleted thousands of old messages, the phantom messages are gone. I THINK this means that the original problem was at the SERVER, not the CLIENT. So I'll mark this as solved, though not explained. Thanks for everybody's attention. Neil
Read this answer in context 👍 0All Replies (3)
Most of the folk I have seen making similar complaints are not aware unread mail in sub folders of the parent is shown if the sub folder is collapsed, but not is the folders are expanded.
This image shows the same trash folder expanded first and then collapsed with different unread and total counts depending on the state.
Thanks, Matt, I appreciate the info. But these folders have no subfolders, so that's not my problem. See the attached image.
Chosen Solution
Stop the Presses! Today the problem is gone! It was one of those days when all the stuff deleted in the last year or so shows back up in the "Junk" and "Trash" folders and has to be deleted all over again. I'm guessing that's the fault of the mail SERVER, which has nothing to do with T'Bird. Anyway, after I re-deleted thousands of old messages, the phantom messages are gone. I THINK this means that the original problem was at the SERVER, not the CLIENT. So I'll mark this as solved, though not explained. Thanks for everybody's attention. Neil
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.