Open
Bug 517169
Opened 15 years ago
Updated 2 years ago
[Autoconfiguration] Creating an account generates a exception
Categories
(Thunderbird :: Account Manager, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: Usul, Unassigned)
References
Details
Just after pressing the create account button (I was creating a gmail imap account) I caught the following in the Error console :
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgSendLater.hasUnsentMessages]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/mail-offline.js :: anonymous :: line 84" data: no]
Comment 1•15 years ago
|
||
With Thunderbird 3.0.3 I have the same Problem. On clicking the create acount button I get this exception:
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgIncomingServer.verifyLogon]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/accountcreation/verifyConfig.js :: verifyLogon :: line 128" data: no]
For me its not possible to create the acount so that the importance is high for me.
OS: Windows Vista, Windows XP on Virtual Box, too.
Thanks a lot.
Comment 2•15 years ago
|
||
I received the same error as comment 1, trying to create a first account on a clean install of Thunderbird 3.1 beta2 build1
I think what the issue was is that the email account name on our server for account e.g. kent@caspia.com is "kent@caspia.com" and not simply "kent" as was guessed. So the name/password was destined to fail.
The correct thing to do is to edit the username before proceeding, but that is not apparent. If you repeat the same thing, you get the same result.
Not sure why I got this today, as on my older systems I do this all of the time without the same exception. BTW the exception is not something subtle in the error console, it is a big fat dangerous looking alert box.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•