We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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 ».

En savoir plus

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

more options

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.

Solution choisie

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

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (1)

more options

Solution choisie

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

Cela vous a-t-il été utile ?

Poser une question

Vous devez vous identifier avec votre compte pour répondre aux messages. Veuillez poser une nouvelle question, si vous n’avez pas encore de compte.