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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Thunderbird's "maximum number of server connections to cache" is not working!?

  • 3 antwoorde
  • 1 het hierdie probleem
  • 5 views
  • Laaste antwoord deur Gigi_diVine

more options

Recently I was experiencing some slowness with emails so I login into my hosting (Siteground) and to my horror I noticed the "running processes" was way over the limit. On Thunderbird I have the "maximum number of server connections to cache" to 1 and all was running smooth until a few days ago. Now I have multiple connections. Is there a new bug on thunderbird? What can I do? HELP!

Recently I was experiencing some slowness with emails so I login into my hosting (Siteground) and to my horror I noticed the "running processes" was way over the limit. On Thunderbird I have the "maximum number of server connections to cache" to 1 and all was running smooth until a few days ago. Now I have multiple connections. Is there a new bug on thunderbird? What can I do? HELP!

All Replies (3)

more options

These are the settings I've had and haven't had a problem with the hosting or server until now, Thunderbird is creating multiple connections to the server.

more options

Is this on a Mac? They are notorious for opening multiple connections and hogging all the bandwidth. :-(

more options

Yes is Mac, but it has been working fine since May until now with the settings I mentioned above, and it was always just one connection per email, now I count 10 per email! Is totally out of control >_<

I first thought it was the new update from TB but I checked on my other computer using 31.7 and it's the same problem.