Thunderbird v 60.4.0 Cannot Download Emails (POP3)
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
People
(Reporter: wcole, Unassigned)
Details
(Whiteboard: [support])
Thunderbird v 60.4.0 (32-bit);
- Click "Get Messages". On status bar "Downloading message 1 of x" appears.
- After about 3 minutes alere "Connection to Server <server-name> was reset" appears. No messages downloaded.
- Error Console sometimes shows nothing, sometime shows:
window.controllers/Controllers is deprecated. Do not use it for UA detection. blank
2019-01-28 17:43:23 gloda.datastore ERROR got error in _asyncTrackerListener.handleError(): 19: constraint failed
log4moz.js:680
2019-01-28 17:43:23 gloda.datastore ERROR got error in _asyncTrackerListener.handleError(): 19: constraint failed.
Yesterday this version seemed to work fine at least once. Today it downloaded 4 messages, posted the connection reset alert, and subsequently will not download any further email.
Email server is not experiencing difficulty.
Thunderbird correctly states the number of messages waiting to be downloaded (as they accumulate, the number shown accurately reflects the accumulation).
Running Thunderbird safe mode (add-ons disabled) has no effect on the problem.
Rebooting the system has no effect.
Turning off Virus scan and firewall (McAfee) has no effect.
Problem does not seem to affect a separate IMAP account.
|
||
Comment 1•6 years ago
|
||
Thanks for the detailed information. These reports tend not to be a bug, and are best explored in the support venue. Had you filed a support request at https://support.mozilla.org/en-US/products/thunderbird ?
I found the culprit: during the first partial download of messages some event occurred (I don't know if it was server- or client-side) that created an email on the server that the web mail UI at my hosting service's site showed as having "From <unavailable>" and "No Subject". Using the webmail UI, I removed the questionable email from the server "Inbox" and then the download of emails by Thunderbird was possible once again.
So the cause of the inability to download any email - one message in the server's "Inbox" with a From field that was "unavailable" - was determined. How that message got created during the first partial download is a mystery to me. And thinking it might have been some sort of security threat I deleted the offending email after a quick look at it via the webmail interface where it had no body, no To, From <unavauilable>. Since the Webmail interface did not allow examining source coding of the email (i.e. all the header info) I could not get a sense of how it originated.
So I guess for the purposes of this problem this case can be closed. If it happens again, I will try to find a way to capture the email in such a way that I can view the source code for it.
Thanks for looking at this report.
Usually you will find your anti virus choked on the malformed email and forced the connection to die. Deleting the mail on the server fixes the issue. Disabling the email scanner in the anti virus product also usually works just as well.
Description
•