Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

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

  • 3 réponses
  • 1 a ce problème
  • 4 vues
  • Dernière réponse par Gigi_diVine

Gigi_diVine
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!

Toutes les réponses (3)

Gigi_diVine
Gigi_diVine Auteur de la question
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.

Zenos
Zenos
more options

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

Gigi_diVine
Gigi_diVine Auteur de la question
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.