295381 - Unread offline newsgroup messages marked as "Read" upon expiry on server

Status: RESOLVED DUPLICATE of bug 201627

(Thunderbird :: Mail Window Front End, defect)

Description

[Gudmund Areskoug]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Thunderbird version 1.0 (20041206)

Either index files corrupt over time, or unread newsgroup messages downloaded
for offline use loose their "Unread" status when they expire on the newsgroup
server.

Two observed examples (both from secnews.netscape.com, both have a 60 day
message expiry date):
1. I've kept the old Firebird NG (with two messages marked "Unread" for...
almost precisely two months today (2005-05-24), i. e. 60 days (the two messages
dates being 2005-03-25).

After accidentally getting a view of one of the messages, I marked it "Unread"
again, and went to another folder. After that, the NG only shows one of those
messages as "Unread" after leaving/returning to the secnews main folder, no
matter how many times I reset the "Unread" status on the other one.

2. I had also kept nine of the messages in n.m.u.general
(netscape.mozilla.user.general) marked "Unread" about 60 days (messages dating
from around 2005-03-16 approximately).

Same thing happens with those messages.

The reset takes place right under my nose, whenever the NG server is polled for
new messages.

Reproducible: Always

Steps to Reproduce:
1. Download a newsgroup message (e. g. "Unread expiry test") for offline reading
from a NG server with an expiry date
2. Make sure it's marked "Unread"
3. Wait until the expiry date is reached
4. Poll the newsgroup for new messages
5. Watch the "Unread" marking disappear from the message "Unread expiry test"

Actual Results:  
The "Unread" marking disappear from the message "Unread expiry test"

Expected Results:  
The "Unread" status should have been kept intact, since the message was
downloaded for offline reading.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gudmund Areskoug]

This bug is still a bug, and its not receiving comments is rather due to the
nature of the bug and the report. 

The bug report says all about the bug, there's nothing much to comment about.

Nothing has happened in ways of fixing the bug, so there's not much to say about
that either, other than for any developer who turns up feeling like doing
something about it.

Comment 3

[ovidiu]

this is very probably related to or even similar to:
bug 79130

Comment 4

[Joshua Cranmer [:jcranmer]]

(In reply to comment #3)
> this is very probably related to or even similar to:
> bug 79130

Not really. It's more of a news-has-no-love-for-offline problem.

Comment 5

[ovidiu]

yep, but is pretty similar to bug 201627 (though posted as rfe..)

Comment 6

[Joshua Cranmer [:jcranmer]]

Good find, ovidiu.

Comment 7

[Joshua Cranmer [:jcranmer]]

Um, I can't type today.