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 stopped working after Version 78.9.0, Build ID 20210322094744 installed itself

  • 1 réponse
  • 1 a ce problème
  • 1 vue
  • Dernière réponse par sfhowes

more options

Thunderbird Installed Version 78.9.0, Build ID 20210322094744 on my Windows 7 SP1 computer yesterday, March ‎24, ‎2021 @ 18.16 CDT. Immediately thereafter I could no longer send or retrieve messages.

  • Attempting to send a message results in the popup message "Status: Connected to outbound.att.net", and the progress bar is green - but - eventually Thunderbird times out and returns the message: Login to account "AT&T" failed . . . Login to server outbound.att.net with username [email protected] failed.

NOTE THAT SBCGLOBAL IS ON THE AT&T SERVER.

This is the first time this has happened after an update. Is there any way to roll back to a previous version or is there an easy fix for this problem?

Thunderbird Installed Version '''''78.9.0''''', Build ID '''''20210322094744''''' on my Windows 7 SP1 computer yesterday, March ‎24, ‎2021 @ 18.16 CDT. Immediately thereafter I could no longer send or retrieve messages. * Attempting to '''''send''''' a message results in the popup message "''Status: Connected to outbound.att.net''", and the progress bar is green - but - eventually Thunderbird times out and returns the message: ''Login to account "AT&T" failed . . . Login to server outbound.att.net with username [email protected] failed''. ''NOTE THAT SBCGLOBAL IS ON THE AT&T SERVER.'' * Attempting to retrieve messages results in the message '''''Error with account [email protected]''''' - '''''Sending of Password for user [email protected] did not succeed. Mail server inbound.att.net responded: Server error - Please try again later'''''. This is the first time this has happened after an update. Is there any way to roll back to a previous version or is there an easy fix for this problem?

Modifié le par RichJan

Toutes les réponses (1)

more options