61034 - Secure newsgroups not appearing in the Subscribe dialog

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Ninoschka Baca]

Build 2000-11-21-04: Win95
Haven't tried Linux or Mac yet.
This problem has been present for awhile.

Overview: Secure newsgroups don't appear in the Subscribe dialog unless first
entering "563" and selecting the "SSL" checkbox in the server panel.

Steps to reproduce:
1. Add a news account which has secure newsgroups (i.e. secnews)
2. Select File|Subscribe and notice that the secure newsgroups do not appear
(i.e. netscape.champions)
3. Open Account Settings and select the Server panel for the news account
4. Enter "563" for the Port and select the checkbox to use SSL
5. Select File|Subscribe

Actual Results: The secure newsgroups do not appear. Even after exiting and
restarting the secure groups still did not appear. The only way I can get this
to work is by entering "563" and selecting the SSL checkbox Before subscribing.

Expected Results: If secure settings are present such as "563" and "SSL" then
the subscribe dialog should show the secure newsgroups.

Comment 1

[scottputterman]

reassigning to sspitzer.

Comment 2

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

the only way to use secure news is to have the port set correctly (usually to
563) and the "use secure connection" checkbox checked.

nbaca, are you saying that if you don't set the port and check the checkbox,
subscribe doesn't work against snews://secnews.netscape.com?  that would be
expected behaviour.

Comment 3

[laurel]

I talked with nbaca, and she already got a group list in subscribe under secnews
(port 119). Then she changed the port to #563 and expected the subscribe dialog
would automatically get the new/proper list for the changed port. Hitting the
refresh button in subscribe should do this...

Comment 4

[Ninoschka Baca]

I selected the Refresh button and the progress bar appears to be doing something
but it never updates. Tried restarting and the Subscribe dialog looks the same
even though it appears to have contacted the server. I finally got it to work
after selecting the "Refresh" button.

In summary I had to exit, restart, open the Subscribe dialog and select the
Refresh button to see the updated list.

Comment 5

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

This worksforme using Windows 2000, 2001011204.

Comment 6

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

This doesn't work on Linux 22001011208 as it does on NT/2000.  In linux you have
to restart Mozilla *and* refresh the server list again.

Sorry...Re-opening.

Comment 7

[scottputterman]

marking nsbeta1-

Comment 8

[jonathan carver]

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7a) Gecko/20040219

this bug reappeared in my zipped build, checked ssl, closed, reopened and no
secure groups show up... unchecked ssl closed out and restarted computer...
checked ssl again... no secure groups... closed and restarted computer again...

still no secure groups appeared in the list upon reentering...

Comment 9

[Riccardo Cretti]

The only way I found to fix this is to delete the file Host in the News server
folder.
If you download again the newsgroups list you will get even the newsgroups
available only with SSL.

Comment 10

[Robert Kaiser]

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 11

[Robert Kaiser]

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

[Robert Kaiser]

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 13

[Robert Kaiser]

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 14

[Robert Kaiser]

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 15

[Robert Kaiser]

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 16

[Robert Kaiser]

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

Comment 17

[Karsten Düsterloh]

This seems to work with Linux SM 2.5.