Closed
Bug 175068
Opened 22 years ago
Closed 22 years ago
authentication is not sent to server if server does not ask
Categories
(MailNews Core :: Networking: NNTP, defect)
Tracking
(Not tracked)
People
(Reporter: alexandre.ho_bugzilla, Assigned: sspitzer)
Details
==> On some news servers, it is not possible to get the groups list. As written in RFC2980, the nntp server sends a "480 Authentication required" message to the client. But if the server does not send this message after the "200 posting OK" message, MozillaNews does not ask the user any authentication data, nor sends anything to the server. The RFC is not clear about the fact that the 480-message must or not be sent by the server, so this is not a real bug, but a logical behavior from the Moz client. Despite the fact that this is just a server setting problem, MSOE is able to work as an end-user would expect. BTW, Sylpheed has the same behavior as Mozilla, and a patch has just been released on sourceforge, enabling to choose whether to authenticate at connexion to the server. -- XandreX
Have you tried "Always request authentication when connecting to this server", located in Edit | Mail & Newsgroups Account Settings | under the 'Server Settings' option for your news account? That should enable what is called 'Pushed Authentication'. Try that, I believe that's what you're looking for.
I cannot see this option in Mozilla 1.0.1 . Anyway, as long as it eventually gets in a release I guess bug is closed. :-) Still, can someone give the target milestone and set the bug to FIXED ?
It's only on the trunk, if you use a any build from this week, you should see it.
bug 39862 *** This bug has been marked as a duplicate of 39862 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Comment 5•22 years ago
|
||
v dupe (featzre only in trunk builds, you can add a hidden pref in 1.0 and it should also work in 1.0)
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•