Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Connect to Gmail TB 52.3.0 has extremely long delays/slow [Mac]

  • 4 odgovora
  • 1 ima ovaj problem
  • 3 prikaza
  • Posljednji odgovor od rjmadaras

more options

Thunderbird 52.3.0 keeps saying “sending login information” and “connecting to imap.gmail.com” but it takes a very long time to connect to Gmail and give me my messages.

Thunderbird 52.3.0 keeps saying “sending login information” and “connecting to imap.gmail.com” but it takes a very long time to connect to Gmail and give me my messages.

Izmjenjeno od Wayne Mery

Izabrano rješenje

rjmadaras said

After I turned everything off, and then restarted my modem, and then my router, and then my computer, the problem went away!

Very strange. Did this only ever happen once?

Did you make any conclusion when of the three things above mostly likely helped?

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (4)

more options

After I turned everything off, and then restarted my modem, and then my router, and then my computer, the problem went away!

more options
more options

Odabrano rješenje

rjmadaras said

After I turned everything off, and then restarted my modem, and then my router, and then my computer, the problem went away!

Very strange. Did this only ever happen once?

Did you make any conclusion when of the three things above mostly likely helped?

more options

The cause of the slow down was the SAVAPI program, which is part of the Avira anti-virus program. The solution was to not run Avira.