Thunderbird 38.2.0 does not automatically check for messages
After upgrading to Version 38.2.0, Thunderbird no longer automatically checks for messages even though it is set to do so every 10 minutes and has been doing that just fine for "forever". When the update was offered, I told TB to perform the update, but the process did something screwy and I got a message along the lines of "can't find Mozilla executable". So, I downloaded a complete copy of 38.2.0 and installed it over the old TB. That process completed correctly, and the program seemed to run after that. Subsequently, I realized that the program was not automatically checking for messages. I can get messages manually. I have checked my server settings and they are unchanged from the past version which worked fine. I have restarted the computer (running Windows 7 Ultimate) several times over a week or so and the problem persists. I'm not sure what to do next. Although this is just a convenience issue, I would still like to get all of the functionality back. Thanks in advance for any help you can provide. Greg
Vybrané riešenie
One problem in this area has been fixed in version 38.3.0. Does anyone still see the problem when using 38.3.0? If not, then we can close this issue.
Čítať túto odpoveď v kontexte 👍 1Všetky odpovede (13)
greghill said
After upgrading to Version 38.2.0, Thunderbird no longer automatically checks for messages even though it is set to do so every 10 minutes and has been doing that just fine for "forever". When the update was offered, I told TB to perform the update, but the process did something screwy and I got a message along the lines of "can't find Mozilla executable". So, I downloaded a complete copy of 38.2.0 and installed it over the old TB. That process completed correctly, and the program seemed to run after that. Subsequently, I realized that the program was not automatically checking for messages. I can get messages manually. I have checked my server settings and they are unchanged from the past version which worked fine. I have restarted the computer (running Windows 7 Ultimate) several times over a week or so and the problem persists. I'm not sure what to do next. Although this is just a convenience issue, I would still like to get all of the functionality back. Thanks in advance for any help you can provide. Greg
I fixed this same problem by going back to 38.1
I too have this problem. Is there a plan to provide a 'fix'?
I fixed the problem by going back to version 38.1. Been refusing the upgrade to 38.2.
Thanks. What is the best way of doing that? Now that I know it is a problem with 38.2, and not my computer, hopefully Mozilla will produce a new version re-activating this automatic download facility?
http://ftp.mozilla.org/pub/thunderbird/releases/
The above web site has all TB releases. Choose the next to last entry and download it.
I got the web site with a google search for 'older mozilla thunderbird versions'
Many thanks, will do. Hope they fix it with the next version.
I don't want to revert, so, i'm here to CONFIRM the problem.
Thunderbird 38.2.0 does NOT check messages automatically in the defined time interval in SERVER OPTIONS in ANY email account.
Upravil(a) Marco Lopes dňa
I was experiencing other problems with Thunderbird 38.0.2, and after many closes and restarts (with no luck) i found that there was a STUCK PROCESS.
I closed thunderbird, killed the process, restarted, et voilá... ALL the issues are gone, including this one!
Upravil(a) Marco Lopes dňa
Marco Lopes said
I was experiencing other problems with Thunderbird 38.0.2, and after many closes and restarts (with no luck) i found that there was a STUCK PROCESS. I closed thunderbird, killed the process, restarted, et voilá... ALL the issues are gone, including this one!
How do you kill the process?
Lindia12 said
How do you kill the process?
I'm in windows, so, i use the TASK MANAGER -> Processes tab.
Vybrané riešenie
One problem in this area has been fixed in version 38.3.0. Does anyone still see the problem when using 38.3.0? If not, then we can close this issue.
Wayne Mery said
One problem in this area has been fixed in version 38.3.0. Does anyone still see the problem when using 38.3.0? If not, then we can close this issue.
I confirm that the issue has been resolved in 38.3.0.