Re: Accessing Secnews
On 08.07.2008 05:08, Ralph Fox wrote:
--- Original Message ---
> On Sun, 06 Jul 2008 15:27:10 -0400, in message <cKWdnU_r2oATgezVnZ2dnUVZ_oLinZ2d@xxxxxxxxxxx>,
> Phillip Jones, CET wrote:
>
>>>>> Then, solution is to edit the configuration ("about:config" in the
>>>>> location/address bar in Seamonkey or
>>>>> Tools->Options->Advanced->General->Config Editor in Thunderbird) and enable:
>>>>>
>>>>> 1) "security.ssl3.rsa_rc4_40_md5" (change to "True")
>>>>> 2) "security.enable_ssl2" (change to "True")
>>>> I can access and post without the certificates
>>>>
>>> But do you still have those lines "true" in about:config ?
>>>
>>>
>> Have bad news report. In SeaMonkey 2 a1pre even if the changes above are
>> made netscape.test.multimedia doesn't exist. there is one called
>> test.moderated but not test Multimedia
>
> There are two different news servers hosted on secnews.netscape.com
> They are normally accessed with different settings...
>
> A. Port = 119
> "[ ] Use secure connection (SSL)" -- not checked
>
> B. Port = 563
> "[X] Use secure connection (SSL)" -- checked
>
> Server 'A' has newsgroup "netscape.test.moderated" but not "netscape.test.multimedia"
> Server 'B' has newsgroup "netscape.test.multimedia"
>
> It appears that you are communicating with server 'A'.
>
> Are your settings as in 'B'?
> If so, then do you have two news server accounts configured in
> SM with the same domain "secnews.netscape.com", the other account
> set up as in 'A'? In this case, try changing one of the two
> domains from "secnews.netscape.com" to "secnews.aoltw.net".
>
>
To see ALL the groups on secnews you only have to have port 563
configured, no need to have a second server configured for port 119. All
the groups can be subscribed to but on port 119, the SSL groups cannot
be seen OR accessed.
--
Jay Garcia Netscape Champion
UFAQ - http://www.UFAQ.org
_______________________________________________
general mailing list
general@xxxxxxxxxxxxxxxxx
https://lists.mozilla.org/listinfo/general