Retrieved newsgroups list does not expand beyond top level newsgroups.

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: Justin Turner Arthur, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(4 attachments)

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021003
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021003

I just installed nightly build 2002100308 upon hearing that bug 141628 had been
fixed earlier today. I was pleasantly suprised to see it actually retrieving the
whole list of newsgroups (via the NNTP LIST request). This is the first time
since netscape 4 perhaps that I've been able to get a newsgroups listing
successfully. However, there is a problem. In the "Subscribe" dialog, it seems
to me like only the top level of newsgroups were listed. Perhaps I am wrong, and
something technically different is happening. One thing I can definetely say is
that there are no sublevels in the tree object. The hostinfo.dat file seems to
contain all of the newsgroups however. I am unsure as to whether this has to do
with seth's patch or not. I will attach a screenshot of the subscribe dialog as
well as a copy of my hostinfo.dat file. The NNTP server I was using was
news.cfw.com on port 119. Like I said earlier, a LIST wouldn't have been able to
be retrieved at all from this server because of bug 141628. I think that this is
a public server, so you're welcome to try it out for yourself.

Good luck!
- Justin

Reproducible: Always

Steps to Reproduce:
1. Load MailNews on build 2002100308.
2. Right-click on NNTP server account, do a subscribe.
3. Wait until list retrieval is complete.
(Reporter)

Comment 1

16 years ago
Created attachment 101608 [details]
Screenshot of the Subscribe dialog after retrieving the list of newsgroups.
(Reporter)

Comment 2

16 years ago
Created attachment 101610 [details]
Zipped copy of hostinfo.dat file for news.cfw.com as described in bug.
(Reporter)

Comment 3

16 years ago
Created attachment 101612 [details]
Zipped NNTP log file. (see comment for more info).

It was requested that I post an NNTP log, so I plopped in the environment
variables and refreshed the newsgroup listing, this is the log file that
resulted. Hope it helps.
Confirming based on screenshot.  I can't tell why this is happening yet, and
can't reproduce.  Obviously, though, you are being hit by it.  I've mailed your
ISP's tech support, asking for a test account.
Confirming based on screenshot.  I can't tell why this is happening yet, and
can't reproduce.  Obviously, though, you are being hit by it.  I've mailed your
ISP's tech support, asking for a test account.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Created attachment 103114 [details]
Screenshot of my Subscribe window after dropping in hostinfo.dat

Weird, Justin.	I can drop this into my specific news server directory
(replacing my current hostinfo.dat) and it seems to thread fine for me.
Justin, I believe we talked in IRC the other day.  Have you tried this since,
with a new profile?
(Reporter)

Comment 8

16 years ago
Yes, indeed I just did. This time, viewing of the retrieved newsgroups was
successful. So as you suggested, it's probably a profile problem. It may have
something to do with the fact that the profile the bug occurs on was a profile
originally converted from Netscape 4.x. I'll be on the lookout for bugs that
this may be a dupe of and maybe I'll try some experiments involving adjusting
the profile a bit.
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail

Updated

10 years ago
Component: MailNews: Subscribe → MailNews: Message Display
QA Contact: stephend → search

Comment 10

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 11

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 12

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Assignee: mail → nobody
QA Contact: search → message-display

Comment 13

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.