183684 - error occoured when I want to connect to any news server

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: NNTP, defect)

Description

[noIdea]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130

I've NNTP proxy server running on port 30119. When I want to connect some
newsgroup I have to enter my server as server name, and name of news server in
the username dialog. It worsk correctly on the others news clients. When I do it
with mozilla, following message appears: "A News (NNTP) error occoured:
newsgroups.borland.com DNEWS Version, S0, posting OK"

Reproducible: Always

Steps to Reproduce:
1. Create new Mail & Newsgroups account.
2. Server sitting are following: server: myproxy, port: 30119, others are all
default
3. Click with rigth button to my acount, and select subscribe
4. Dialogs "Prompt" appears. Now I insert "newsgroups.borland.com", and click OK.


Actual Results:  
Error occoured: "A News (NNTP) error occoured: newsgroups.borland.com DNEWS
Version, S0, posting OK"

Expected Results:  
Connect to server, and get a list of newsgroups.

Comment 1

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

noIdea, could you please run a protocol log on your build (see
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#nntp for
instructions).  This will help us isolate the problem.  Thanks.

Comment 2

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

0[771cc0]: (2aeb970) setting busy to 0
0[771cc0]: (2aeb970) creating
0[771cc0]: (2aeb970) initializing, so unset m_currentGroup
0[771cc0]: (2aeb970) setting busy to 1
0[771cc0]: (2aeb970) opening connection to proxy.lynx.sk on port 30119
0[771cc0]: (2aeb970) setting busy to 1
0[771cc0]: (2aeb970) ParseURL
0[771cc0]: (2aeb970) fullPath = /*
0[771cc0]: (2aeb970) m_messageID = (null)
0[771cc0]: (2aeb970) group = *
0[771cc0]: (2aeb970) commandSpecificData = (null)
0[771cc0]: (2aeb970) m_key = -1
0[771cc0]: (2aeb970) Next state: NNTP_RESPONSE
0[771cc0]: (2aeb970) Receiving: 200 Hello you can post or not
0[771cc0]: (2aeb970) Next state: NNTP_LOGIN_RESPONSE
0[771cc0]: (2aeb970) Next state: NNTP_SEND_MODE_READER
0[771cc0]: (2aeb970) Sending: MODE READER

0[771cc0]: (2aeb970) Next state: NNTP_RESPONSE
0[771cc0]: (2aeb970) Receiving: 450 Authorization required for this command
0[771cc0]: (2aeb970) Next state: NNTP_BEGIN_AUTHORIZE
0[771cc0]: (2aeb970) ask for the news username
0[771cc0]: (2aeb970) use newsgroups.borland.com as the username
0[771cc0]: (2aeb970) Sending: AUTHINFO user newsgroups.borland.com

0[771cc0]: (2aeb970) Next state: NNTP_RESPONSE
0[771cc0]: (2aeb970) Receiving: 200 newsgroups.borland.com DNEWS Version , S0,
posting OK 
0[771cc0]: (2aeb970) Next state: NNTP_AUTHORIZE_RESPONSE
0[771cc0]: (2aeb970) Next state: NNTP_ERROR
0[771cc0]: (2aeb970) ClosingConnection
0[771cc0]: (2aeb970) Sending: QUIT

0[771cc0]: (2aeb970) ClosingSocket()
0[771cc0]: (2aeb970) CleanupAfterRunningUrl()
0[771cc0]: (2aeb970) setting busy to 0
0[771cc0]: (2aeb970) ClosingSocket()
0[771cc0]: (2aeb970) CleanupAfterRunningUrl()
0[771cc0]: (2aeb970) setting busy to 0
0[771cc0]: (2aeb970) destroying

Comment 3

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

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