Comment 48 for bug 322256

(In reply to comment #46)
> Sorry if I insist on this: I think the .rc file is updated correctly, it is
> the view "threads with unread" that is not correct.

Have you actually *looked* at the .rc file when this happens?

The .rc file is *where* the information on what is and is not read displayed in the folder pane is stored.

If you bring up the .rc file in an editor on a group where you've marked everything as read and posts still show as unread, you'll see the problem.

Here's a sample .rc file from my system, for newsgroups on the Baen server:

baen.1632Tech: 1-155504,155512,155516-155518,155526,155534,155543
baen.administrivia: 1-15915
baen.bar: 1-61263,61268-61270,61275,61277
baen.books: 1-17530
baen.buships: 1-28405,28420,28422,28423,28428,28430,28432-28434,28437
baen.classicsf: 1-1293
baen.EBookReader: 1-1836
baen.faq: 1-91
baen.FutureTech: 1-14769
baen.honorverse: 1-39405
baen.space: 1-4431

This: "baen.space: 1-4431" indicates all messages are read.

This: "baen.bar: 1-61263,61268-61270,61275,61277" indicates that messages 1-61263 are read, 61264-61267 are *not* read, etc.

Look at the .rc file for a group which shows an unread message count in the folder pane but all messages are in fact read, and you'll see that the line in the .rc file for that group is wrong.

When I see that problem, I can correct it by editing the .rc file to include the correct range of read messages. When I restart TB, the problem is gone.

What I *can't* reproduce is *why* a particular entry in the .rc file isn't properly updated. It happens randomly, occurs on any of the six news servers I have configured, and doesn't affect all groups on the server.
______
Dennis