Today I made a quick test using version 38.5.0-1~deb7u1+7.0trisquel2 of
Icedove.
The test involved removing my existing receiving account setup (be it IMAP or
POP3), opening the errors console (which can be located at the Icedove's
menu, in the Tools menu, or by pressing Ctrl + Shift + J), making the errors
console display every message, and the configure the receiving account again.
Note that since I have issues with the receiving process, I didn't remove the
sending account information, otherwise I would have to configure other
sending account just to be able to remove and reconfigure the one I would
normally use.
So in the errors console I get the following messages before using the
automatic server configuration discovery for the account:
# Start of log.
While registering XPCOM module
file:///usr/lib/icedove/components/libdbusservice.so, trying to re-register
CID '{75a500a2-0030-40f7-86f8-63f225b940ae}' already registered by .
Hour: 04-01-2016 20:41:45
Alert: Mutation events shouldn't be used anymore. Instead, use
MutationObserver.
Source file: chrome://calendar/content/widgets/calendar-widgets.xml
Line: 496
Hour: 04-01-2016 20:41:46
Error: TypeError: tab is undefined
Source file: chrome://messenger/content/tabmail.xml
Line: 1067
# End of log.
Then, during the usage of the automatic server configuration discovery for
the account:
# Start of log.
Hour: 04-01-2016 20:43:27
Error: The XML file doesn't contain an email account configuration.
Source file: resource:///modules/errUtils.js
Line: 35
# Last message repeats 2 times.
Hour: 04-01-2016 20:43:31
Error: Not Found
Source file: resource:///modules/errUtils.js
Line: 35
Hour: 04-01-2016 20:43:32
Error: MX lookup would be no different from domain
Source file: resource:///modules/errUtils.js
Line: 35
# End of log.
Then, as OpenMailBox users might already know, once the discovery is
finished, we need to supply our email address as the username for the IMAP,
POP3, and SMTP servers, and so I did, and after inserting my password and
unchecking "Remember password", I was expecting some feedback in the errors
console. Surprisingly, nothing showed up in the errors console. However, the
bug still persists since a normal user will face a warning telling him that
the username or password are incorrect, and which will not allow the window
to close even after the "Finish" but is clicked. The window only closes if
the user cancels the configuration or configures the account manually using
the advanced configuration. But still after configuring the account, he won't
be able to receive emails (for those who are unable to receive, at least).
Interestingly, when telling Icedove to enter the advanced configuration, the
errors console shows the following:
# Start of log.
Hour: 04-01-2016 21:08:58
Error: [Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIMsgFolder.getStringProperty]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2790"
data: no]
Source file: chrome://messenger/content/folderPane.js
Line: 2792
# Last message repeats 1 times.
# End of log.
When I accept the configuration and click at the inbox of my still-not-loaded
IMAP account, the errors console shows the following:
# Start of log.
Hour: 04-01-2016 21:13:00
Error: [Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIMsgFolder.getStringProperty]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2790"
data: no]
Source file: chrome://messenger/content/folderPane.js
Line: 2792
# Last message repeats approximately 53 times.
# End of log.
I hope this has proven to be useful, even if it serves to rule something out
(that is, to discard some possibility which is in the minds of the
developers).
Todo: Do the same procedure with a previous version of Icedove that used to
behave well, in order to check whether the errors presented here are unique
to the upgraded version or not.
