Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

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

  • 1 valiny
  • 1 manana an'ity olana ity
  • 1 view
  • Valiny farany nomen'i 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?

Novain'i RichJan t@

All Replies (1)

more options