(In reply to comment #48)
[...]
> This: "baen.bar: 1-61263,61268-61270,61275,61277" indicates that messages
> 1-61263 are read, 61264-61267 are *not* read, etc.
[...]
They aren't read, and, in the case concerned by this bug, cannot be read because they don't exist anymore. I think there are in theory two possible fixes for this bug:
a) Leave the rc as it is, but don't count messages that don't exist on the server anymore when computing the number of unreads for a group; or
b) when it is found that a message doesn't exist anymore, mark it as read in the rc file so the mailer will remember that that message isn't "unread" (in the sense of being available for reading).
I think (b) would be easier to implement, since (a) wouldn't leave a memory of which "holes" in the list correspond to messages that cannot be read anymore.
(In reply to comment #48) 61268-61270, 61275,61277" indicates that messages
[...]
> This: "baen.bar: 1-61263,
> 1-61263 are read, 61264-61267 are *not* read, etc.
[...]
They aren't read, and, in the case concerned by this bug, cannot be read because they don't exist anymore. I think there are in theory two possible fixes for this bug:
a) Leave the rc as it is, but don't count messages that don't exist on the server anymore when computing the number of unreads for a group; or
b) when it is found that a message doesn't exist anymore, mark it as read in the rc file so the mailer will remember that that message isn't "unread" (in the sense of being available for reading).
I think (b) would be easier to implement, since (a) wouldn't leave a memory of which "holes" in the list correspond to messages that cannot be read anymore.