Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Thunderbird stopped working after Version 78.9.0, Build ID 20210322094744 installed itself

  • 1 Antwort
  • 1 hat dieses Problem
  • 17 Aufrufe
  • Letzte Antwort von 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?

Geändert am von RichJan

Alle Antworten (1)

more options