User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13 Build Identifier: 2.0.0.12 (20080213) I do not have a static IP address, so sometimes if my connection gets reset my ip address changes. When this happens and I am browsing newsgroups, my authentication fails because it thinks I am connecting from 2 ip addresses. If I give it a couple of minutes and retry it works. However Thunderbird insists I re-enter my username and password, this is a real pain as both my username and password are a string of alpha numeric characters, very hard to remember. It seems to remove the saved password from its memory when it encounters the above error. Reproducible: Always Steps to Reproduce: 1. Sign in to a newsgroup account that only allows connections from one IP address. Tell thunderbird to remember your username / password. 2. Change your external IP address while connected. 3. Request another article, and you will receive an error about to many simultaneous IP address. 4. Retry after a minute and thunderbird will prompt you for your password again. Actual Results: The username and password were no longer stored. Expected Results: It should only prompt me for a new password if it receives a password related to my credentials. 'Too many simultaneous IP address' is not a problem with the password, so it should not be removed.

I cannot reproduce this, because I do not know how your particular news server responds in this situation. For some types of error, Thunderbird reports the error and retries using the same username and password. For other types of error, Thunderbird asks you to confirm the stored username and password. You do not have to retype them, because Thunderbird supplies them in the prompt. So the summary, "Username and password are not remembered after error browsing newsgroups", is certainly too general. To investigate further, make a connection log for a session in which this problem occurs. Attach the log file in this bug report. See: http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html

This needs to be done for all protocols in general. See bug 435306.