Bug 1706926 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Hello Sander, does this require starting from blank with no accounts set up?

wfm on win10, 90.0a1 (2021-04-22) (64-bit)

I was also failing to reproduce this on win10, 89.0b1 (32-bit).

Once got this on beta: (trying to re-add an imap account which I already have, but it should tell me that, not this)
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgAccountManager.createIncomingServer]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/accountcreation/verifyConfig.js :: verifyConfig :: line 70"  data: no]
Revision 1 by
on 
Hello b.bergman, does this require starting from blank with no accounts set up?

wfm on win10, 90.0a1 (2021-04-22) (64-bit)

I was also failing to reproduce this on win10, 89.0b1 (32-bit).

Once got this on beta: (trying to re-add an imap account which I already have, but it should tell me that, not this)
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgAccountManager.createIncomingServer]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/accountcreation/verifyConfig.js :: verifyConfig :: line 70"  data: no]

Back to Bug 1706926 Comment 2