Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

sign-in notification keeps popping up for every email send causing time-out

  • 2 antwoorden
  • 1 heeft dit probleem
  • 11 weergaven
  • Laatste antwoord van DJakth59

DJakth59
DJakth59
more options

For the past few months, I have been getting sign-in notifications that do not seem to work or go away every time I send an email through Thunderbird. It doesn't seem to matter which gmail account I use, it brings up this request for sign in to proceed to Mozilla Thunderbird (Capture1). Pressing Next does nothing, If I don't press anything, the following send error happens (Capture2). Never used to happen at all, but happens with old and new accounts.

Is there something in the settings that isn't right?

For the past few months, I have been getting sign-in notifications that do not seem to work or go away every time I send an email through Thunderbird. It doesn't seem to matter which gmail account I use, it brings up this request for sign in to proceed to Mozilla Thunderbird (Capture1). Pressing Next does nothing, If I don't press anything, the following send error happens (Capture2). Never used to happen at all, but happens with old and new accounts. Is there something in the settings that isn't right?
Gekoppelde schermafbeeldingen

Gekozen oplossing

The version was 52.1.1, but has been upgraded now to 52.3. I believe this problem has been fixed, but will continue to test it to make sure.

Dit antwoord in context lezen 👍 0

Alle antwoorden (2)

user01229325
user01229325
more options

This is a symptom of someone using Gmail and an old version of Thunderbird. If using a version older than v52.x, upgrade.

DJakth59
DJakth59 Vraageigenaar
more options

Gekozen oplossing

The version was 52.1.1, but has been upgraded now to 52.3. I believe this problem has been fixed, but will continue to test it to make sure.