192374 - New usenet message count displays but no new messages downloaded

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: NNTP, defect)

Description

[Tyson Ackland]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130

If you have new usenet messages set to auto download every interval, eg 5 mins,
the "Name" pane on the left displays the number of new messages but the actual
message headers are not displayed until you deselect the newsgroup and click on
it again.

Reproducible: Always

Steps to Reproduce:
1.Setup auto-checking on the usenet server (eg 5 mins)
2.After 5 mins, a count of new messages is displayed but scrolling thru the list
shows no new messages!
3.Click on something else eg another newsgroup or the mail inbox etc and then
click back on the desired newsgroup and now the messages are displayed.

Actual Results:  
New usenet messages now displayed.  Problem happens every time new messages arrive.

Expected Results:  
Display the new messages in the message list without requiring the
deselection/reselection process described.

Default theme used.

Comment 1

[gene smith]

I can confirm this. Well, not exactly sure about the numbers going up (which
they probably do) but I definitely see that to get new news messages listed I
have to select some other folder in mailnews and come back to the orignal one of
interest. Even hitting the "get new messages" button does not work. (With
tcpdump I can see something going out every X minutes per the server settings,
but I *never* see new message listed when this happens.)

Possible twist. I am connecting to newserver "localhost" (127.0.0.1) on port 119
which is forwarded via a ssh tunnel to gmane.org's port 119 via a friendly sshd
server on the internet. Site firewall does not allow direct connections to port
119 but does allow 22. However, I think, but am not certain, that I have
observed this when directly connected to my isp's news server from home. 
(Using win2k/moz 1.6 here, linux/moz 1.6 at home.)

Comment 2

[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 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.