User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; rv:1.7.3) Gecko/20040914 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; rv:1.7.3) Gecko/20040913 Changing the POP3/IMAP login name using account maintenace creates/changes a '.realUserName' value in prefs.js but the actual login continues to use the original '.userName' value from prefs.js Reproducible: Always Steps to Reproduce: 1. Create a new POP3 (or IMAP) account in MailNews with the wrong login name 2. Invoke account maintenance and correct the login name 3. Try to connect to account with corrected login name Actual Results: mail server reports incorrect username/password Expected Results: mail server should accept login Either '...server#.realUserName' should be used in preference to '...server#.userName' or the code should not create 'realUserName' when modifying the login name.
When POP3, if username change was done thru UI(Account Settings), my Mozilla was used, and is using .realuserName correctly. Is .userName really used in login? Isn't it Bug 277529 problem? (password problem, instead of username problem) Try nexts. (1) Delete password entry for the POP3 account thru password manager. (2) POP3 access (3) Delete password entry for the IMAP account thru password manager. (4) IMAP access For IMAP, similar symptom is reported to Bug 277529 comment #6. Do you mean "<Value in .userName in prefs.js> at <Server_Name>" like message was displayed when login failure, instead of "<Value in .realuserName in prefs.js> at <Server_Name>"? Can you get protocol log for IMAP? (Don't paste long log. Attach file, please) See http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap for log. Don't forget to change "protocol:5" to "IMAP:5" when IMAP. Please note that log file is overlayed on restart.
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.