We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Thunderbird 38.2.0 does not automatically check for messages

  • 13 replies
  • 18 have this problem
  • 8 views
  • Last reply by Marco Lopes

more options

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

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

Chosen solution

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.

Read this answer in context 👍 1

All Replies (13)

more options

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

more options

I too have this problem. Is there a plan to provide a 'fix'?

more options

I fixed the problem by going back to version 38.1. Been refusing the upgrade to 38.2.

more options

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?

more options

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'

more options

Many thanks, will do. Hope they fix it with the next version.

more options

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.

Modified by Marco Lopes

more options

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!

Modified by Marco Lopes

more options

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!
more options

How do you kill the process?

more options

Lindia12 said

How do you kill the process?

I'm in windows, so, i use the TASK MANAGER -> Processes tab.

more options

Chosen Solution

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.

more options

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.