Thunderbird does not fetch new e-mail automatial when been inactive a while, after resuming from sleep.
I have a new powerful computer with windows 8 and installed Thunderbird. Great product, but does not work properly. When I am active on the computer new messages comes automatically and immediately. I have set that Thunderbird shall look for new messages every 5th minute. Over night I am still logged on but the computer is probably sleeping, no new messages appears in the morning. When using the button "Fetch messages", ("Hämta meddelanden" in swedish), nothing happens. The application thinks and thinks and at the end I close Thinderbird and try to restart it. Then I get the message that Thinderbird is already started and I cannot open the application. The only solution I have found out to get my mails is to "kill" Thunderbird in the activity manager and then start Thunderbird again. When doing that all new messages is fetched immediately and automatically when starting the application. What is the problem? Help please.
Thomas Sääf, Stockholm
Wayne Mery trɔe
All Replies (7)
Why not shut Thunderbird down when you go to bed? You can start it up again the next morning and get the messages.
Sounds like Thunderbird's flakeyness in the networking area.
Does fetch work if you do File | Offline | Work offline, and do the same thing a second time? (this disables and reenables the network donnection.
Wayne Mery said
Sounds like Thunderbird's flakeyness in the networking area. Does fetch work if you do File | Offline | Work offline, and do the same thing a second time? (this disables and reenables the network donnection.
I have the same problem on OSX Yosemite, and going offline and then online does clear the problem.
araybo said
Wayne Mery saidSounds like Thunderbird's flakeyness in the networking area. Does fetch work if you do File | Offline | Work offline, and do the same thing a second time? (this disables and reenables the network donnection.I have the same problem on OSX Yosemite, and going offline and then online does clear the problem.
Good to know. In that case your problem is https://support.mozilla.org/en-US/questions/1079754
It's unlikely saaft, the original reporter has the same problem. The problem you have does not exist on linux.
saaft, what's up with your issue?
Wayne Mery said
Sounds like Thunderbird's flakeyness in the networking area. Does fetch work if you do File | Offline | Work offline, and do the same thing a second time? (this disables and reenables the network donnection.
Wayne Mery said
araybo saidWayne Mery saidSounds like Thunderbird's flakeyness in the networking area. Does fetch work if you do File | Offline | Work offline, and do the same thing a second time? (this disables and reenables the network donnection.I have the same problem on OSX Yosemite, and going offline and then online does clear the problem.
Good to know. In that case your problem is https://support.mozilla.org/en-US/questions/1079754
It's unlikely saaft, the original reporter has the same problem. The problem you have does not exist on linux.
Thanks. Reverting to 38.1.0 has solved the problem for me on OSX. I see that Saaft posted his problem in June, so that will probably not be a solution for him.
araybo said
Wayne Mery saidaraybo saidWayne Mery saidSounds like Thunderbird's flakeyness in the networking area. Does fetch work if you do File | Offline | Work offline, and do the same thing a second time? (this disables and reenables the network donnection.I have the same problem on OSX Yosemite, and going offline and then online does clear the problem.
Good to know. In that case your problem is https://support.mozilla.org/en-US/questions/1079754
It's unlikely saaft, the original reporter has the same problem. The problem you have does not exist on linux.
Thanks. Reverting to 38.1.0 has solved the problem for me on OSX. I see that Saaft posted his problem in June, so that will probably not be a solution for him.
Correction: reverting to 38.1.0 does not solve the problem. Furthermore, my experience differs from https://support.mozilla.org/en-US/questions/1079754 because when it stops working, even manually requests fail.