User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7a) Gecko/20040218 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7a) Gecko/20040218 My primary NNTP server, news.east.earthlink.net, is frequently down for short periods of time. This wouldn't normally a problem, except that the user ID and password (which were supposed to be saved by the password manager) must be re-entered each time after the client encounters a server that is temporarily unreachable. Reproducible: Always Steps to Reproduce: 1. Create newsgroup account. 2. When prompted, enter user ID and password. Select "Use Password Manager to remember this value." for both user ID and password. 3. Read newsgroups. Close and restart mozilla. 4a. If Mozilla can immediately connect to the NNTP server, groups can be read without having to re-enter user ID or password (this is the expected behavior.) 5a. Continue with step 3. 4b. If Mozilla can't connect to the NNTP server right away, Mozilla will (i) give an error message: "A News (NNTP) error occurred: News serer temporarily unavailable; please try again in a few minutes (ELAuth Errored)" and (ii) prompt again for the NNTP account user ID and password. 5b. Keep asking for user ID and password until connection can be established. 6b. Continue with step 3. Actual Results: See step 5b above. Expected Results: Mozilla News should remember the user ID and password for NNTP accounts in the same way it remembers these values for IMAP4 and POP3 accounts. (E.g., when a POP3 or IMAP server is temporarily unavailable, a user does NOT have to re-enter their user ID and password the next time the server is available again.) In Password Manager, the user ID for NNTP accounts is given only as "<>" (also see <http://bugzilla.mozilla.org/show_bug.cgi?id=201750#c4>.)
This bug is particularly bothersome for Comcast users. I've had to re-enter my username and password from 3 to 30 times per hour whenever nntp://newsgroups.comcast.net returns an intermittant authentication error. http://forums.comcast.net/thread.jspa?threadID=31297&start=30&tstart=0
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/
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.