27474 - handle expired news/nntp articles

Status: VERIFIED FIXED

(MailNews Core :: Backend, defect, P3)

Description

[laurel]

This is a feature tracking bug to track implementation of handling expired news
articles.

Even when opening a newly subscribed group for the first time, I am getting
expired articles.  We should not be downloading headers for expired or cancelled
articles. 

Another part of expired article handling would be similar to what 4.x does: when
encountering an expired article in reading through list of already downloaded
headers, 4.x provided a link that when clicked "removed all expired articles"
from your local database, so you wouldn't see them again in the thread pane. 
There were a couple lingering bugs with 4.x on this removal process, but I think
it was good to have a method to get rid of those expired articles.

Comment 1

[(not reading, please use [e-mail] instead)]

accepting, marking m15 

Comment 2

[(not reading, please use [e-mail] instead)]

moving to m16.

Comment 3

[selmer (gone)]

The critical part of this for beta2 is not downloading a million expired headers.

Comment 4

[David :Bienvenu]

I don't believe it's possible to download headers for expired articles - if 
they're expired, the news server should NOT give you the headers. There's no way 
for us to know before the fact that an article is expired or not - all we can do 
is look at the lowwater mark and the highwater mark and download the articles in 
between. 

Comment 5

[(not reading, please use [e-mail] instead)]

david b. right.  the server won't give you expired articles.

this bug is to make sure I fix what happens when you click on a message in your
thread pane the corresponds to a message that has been cancelled.  this will
includes supporting "?list-ids" urls.

Comment 6

[selmer (gone)]

Syncing priority with marketing.  Moving to P2 to connote "In" for beta2.

Comment 7

[(not reading, please use [e-mail] instead)]

not a "feature", we are just not handling this correctly.

Comment 8

[Michael La Guardia]

Putting on nsbeta2- radar.

Comment 9

[(not reading, please use [e-mail] instead)]

moving to m17, since it is not a m16 blocker.

Comment 10

[David :Bienvenu]

nominating for nsbeta3

Comment 11

[laurel]

possible item for relnote2

Comment 12

[scottputterman]

Mail Triage is marking [nsbeta3-]

Comment 13

[selmer (gone)]

Laurel, please include a comment explaining why you think this should be
accepted for RTM.  This should be standard practice for nominations.  Thanks!

Comment 14

[laurel]

That was supposed to be relnoteRTM.

Comment 15

[selmer (gone)]

Thanks :-)

Comment 16

[Kristi Fredrickson]

This has been nominated to for inclusion in the "Upgrading to Netscape 6" 
document, which summarizes for existing Commuinicator customers the features that 
change when they move to N6. What should I tell them is different about the way 
N6 handles expired news articles?

Comment 17

[laurel]

mass change of huang's news bugs to stephend.

Comment 18

[Tobias Burnus]

How about a mozilla-X, X<1 milestone?
If you have a highly active group on a server which saves the articles rather
short this is annoying.

Comment 19

[[e-mail] (gone - use [e-mail] instead)]

mail3

Comment 20

[scottputterman]

marking nsbeta1+ and moving to mozilla0.9 milestone

Comment 21

[(not reading, please use [e-mail] instead)]

part of this bug is fixed:  you will now see the special message about reading
an expired article with a link to remove all expired articles.

currently that link doesn't work right.

news://host/group?list-ids urls don't work, I've logged that bug.

I need to investigate if we are downloading expired or cancelled articles.  can
you confirm if we are still doing that?

Comment 22

[David :Bienvenu]

like I said before, you can't download expired/cancelled articles - the server
shouldn't give them to you. And if it does, there's no way for us to know before
hand that an article has expired (other than the low water mark, which I believe
we do pay attention to). It's not really relevant, anyway. An article can
expire/be cancelled after we've downloaded the header. 

Comment 23

[(not reading, please use [e-mail] instead)]

based on bienvenu's comments, marking this fixed.

the only remaining issue is the that "?list-ids" urls don't do the right thing.

that is covered in bug #63248

Comment 24

[[e-mail] (gone - use [e-mail] instead)]

I haven't run across an expired article yet after visiting 10 newsgroups on 2
different servers on all platforms.  Marking VERIFIED FIXED.  Windows 2000
2000122105, Mac 2000122105 and Linux 2000122108.

Comment 25

[[e-mail] (gone - use [e-mail] instead)]

Just to clarify the 2nd part of Laurel's filing, I verified that viewing 
expired articles (as a result of a different profile posting then cancelling) 
does indeed bring up the HTML "click here to remove all expired articles".  
Verified on all of today's builds.