Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Thunderbird stuck in "sending access information" on Ubuntu / Gmail

  • 1 resposta
  • 0 tem este problema
  • 172 visualizações
  • Última resposta de Gustavo Mitamura
  • Resolvidas

Since yesterday, Thunderbird has been really slow and seemingly unable to properly authenticate with our Google Workspace account, but this seems to be happening only on Ubuntu machines, not on Windows. When I tried sending an email, it seemed to work (as I was able to verify on web gmail that it was indeed sent), but it is also stuck on sending access information, and then it will throw an error saying it failed to authenticate against imap.gmail.com

I already removed and re-added the account, but the problem persists. I'm using all default configurations.

Thunderbird Version 128.5.1esr (64 bits) Ubuntu 24.04.1 LTS

Thanks.

Since yesterday, Thunderbird has been really slow and seemingly unable to properly authenticate with our Google Workspace account, but this seems to be happening only on Ubuntu machines, not on Windows. When I tried sending an email, it seemed to work (as I was able to verify on web gmail that it was indeed sent), but it is also stuck on sending access information, and then it will throw an error saying it failed to authenticate against imap.gmail.com I already removed and re-added the account, but the problem persists. I'm using all default configurations. Thunderbird Version 128.5.1esr (64 bits) Ubuntu 24.04.1 LTS Thanks.

Solução escolhida

It seems to have been an outage on gmail's part, because the problem seemed to have solved itself.

Ler esta resposta 👍 0

Todas as respostas (1)

Solução escolhida

It seems to have been an outage on gmail's part, because the problem seemed to have solved itself.