Symptoms: - Attempt to check email, no email obtained. - The following error appears in the error console (accessible under the tools menu): Error: malformed URI sequence file:///C:/Archivos%20de%20programa/Mozilla%20Thunderbird/components/nsLoginManagerPrompter.js Line: 469 If the error doesn't appear your issue isn't this bug. Workaround: - Go into options or preferences. - Select Advanced, followed by General. Then select the Config Editor... button. - This will bring up a window, in the Filter part enter "userName" (without the quotes). - Look at entries such as: mail.server.server3.userName mail.server.server3.realuserName - Ensure that both of these do not contain non-ascii characters. If they do you can modify them by right-clicking and selecting Modify. - Restart Thunderbird You should then be able to access your account, although you may need to re-enter your password.
Some more debugging shows that I think this is only a problem during upgrade. I think we managed to change how we're storing the username in prefs.js possibly unicode versus UTF-8 or something like that. STR: - In Thunderbird 2, create an account with a username like "sé", the non-ascii character is important. - Load Thunderbird 3.1 try and get new mail (it doesn't matter if it should succeed or not). => Result is the error message in comment 0 on the console and no password dialog. I'm not sure there is much we can do about this, not without breaking existing users. If David or Neil have any thoughts, they would be welcome.
Mozilla 1.6 stores the realusername in ISO-8859-1 format.
If you are faced with the problem, open the file nsLoginManagerPrompter.js and go to line 469. Add // to comment out the decodeURI function. I'm running thunderbird on mac os. This solves the problem for me... Just a quick and dirty workaround.
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.
You need to log in before you can comment on or make changes to this bug.