Last Comment Bug 24592 - Newsgroup message counts don't reflect expired messages.
: Newsgroup message counts don't reflect expired messages.
Status: RESOLVED DUPLICATE of bug 79130
Product: MailNews Core
Classification: Components
Component: Networking: NNTP (show other bugs)
: Trunk
: All All
P3 normal with 3 votes (vote)
: Future
Assigned To: Nobody; OK to take it and work on it
: 290826 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2000-01-20 16:48 PST by Suresh
Modified: 2009-01-22 10:17 PST (History)
6 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Suresh 2000-01-20 16:48:01 PST
Number of msgs in News Server is NOT reflected properly in pop-up window while 
downloading the headers. I beleive the messenger client reads the total number 
of headers from the newsrc file or the News server responds wrong numbers.

Steps to reproduce:
1. Add "news" newsserver to the account.
2. Subscribe to "netscape.public.mozilla.mail-news" newsgroups.
3. When you click on this newsgroup to download the headers, a pop-up window 
shows up and reads "There are 1728 headers in the server. Do you want to 
download all or 500 headers". (Shown in check box with OK and Cancel button).

4. The reality is only 220 headers are present in the newsserver. The pop-up 
window should read "There are 220 headers in the server...". 

Build Date: 1/19/00 Linux commercial build.
Comment 1 User image (not reading, please use instead) 2000-01-20 20:00:19 PST
for completeness:  

this problem is in 4.x with news://news/netscape.public.mozilla.mail-news

they recently purged the old articles on news,, and (they are all the same machine)

Comment 2 User image (not reading, please use instead) 2000-02-02 11:19:02 PST
4.x does the same thing.

moving to m20, and I will investigate then.
Comment 3 User image lchiang 2000-06-09 23:58:03 PDT
4.x has the same problem - move to target milestone future
Comment 4 User image laurel 2000-11-20 16:02:52 PST
mass change of huang's news bugs to stephend.
Comment 5 User image Albert White 2004-03-13 20:03:31 PST

I've noticed this on 1.7alpha also.

From a brief investigation it seems to occur in this scenario.

From telnetting to the news server:

LIST ACTIVE 329201 318904 y

Mozilla appears to interpret this to mean that there are 10297 (329201-318904)
messages to download.

However the LISTGROUP command returns the number of messages and the relavent
message ID's.
211 articles follow

The RFC's (977 & 2980) do not state that the difference in message id's in the
LIST output should be all available messages, nor that LISTGROUP should return a
sequential list.

It appears that mozilla should base its calculation on the number of headders to
download based on the output of the LISTGROUP command and not LIST. Then
retrieve the messages in the output from LISTGROUP and not just increment
m_articleNumber based on the first article from LIST.

Comment 6 User image (not reading, please use instead) 2007-06-21 14:23:11 PDT
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Comment 7 User image Joshua Cranmer [:jcranmer] 2008-05-29 16:12:09 PDT
*** Bug 290826 has been marked as a duplicate of this bug. ***
Comment 8 User image Joshua Cranmer [:jcranmer] 2008-05-29 16:14:57 PDT
I'm simplifying this bug's summary for easier future duping. This bug is essentially one of the two core, known, not-quite-a-bug newsgroup count bugs. What this is reflecting is that the news server is providing us a count estimate that does not reflect the holes produced by expired articles.
Comment 9 User image Tony Mechelynck [:tonymec]. (NEEDINFO me if you want my attention) 2008-05-29 16:47:36 PDT
See workaround in bug 294754 comment #3 (in a bug which, by recursion, finally became duped to this one).
Comment 10 User image Rimas Kudelis 2008-05-30 04:13:02 PDT
Joshua, could the bug 79130 be a dupe of this too?
Comment 11 User image Joshua Cranmer [:jcranmer] 2008-06-26 08:14:43 PDT
After further thought, I've come to the conclusion that this and bug 79130 are the same issue. Although 79130 is newer, it is more discussion, and, for that reason, this will be a dupe of that one.

*** This bug has been marked as a duplicate of bug 79130 ***

Note You need to log in before you can comment on or make changes to this bug.