Could my gmail SMTP errors be from yesterday's Workspace outage?

[LonnieFry]

Yesterday afternoon, I tried to send an email in Thunderbird like I often do, but it returned an SMTP login error. I hadn't seen that in a super long time. I found out that Google had a glitch with certain outgoing emails and attachments. But I tried all sorts of account resets on the Thunderbird email client, which supports OAuth2. I have a 2nd PC setup just like this one, and it was sending emails fine. It's just this one account on one client.

Login to server smtp.gmail.com with username (my legacy domain gmail account) failed.

Login to server smtp.gmail.com with username (my legacy domain gmail account) failed.
Retry, Enter New Password, Cancel

No matter of resetting on this end works. I even deleted and then re-added the SMTP outgoing server. Same error. When I temporarily switched to a 2nd gmail account, the email was sent, but it caused spoofing error messages for the recipient ... who  laughed that I was caught impersonating ... myself ... by Google.

[Jan-Carlos]

I think is because your trying to autenticate with your account password.
Maybe you have to use the app password for that:
https://support.google.com/accounts/answer/185833?hl=en&sjid=13760844992466536444-SA

[LonnieFry]

Well, my email program uses the OAuth2. It's not the same as App passwords. Basically, you enter your credentials, the software detects that you have selected OAuth2, and then it authenticates in a little window to the Google website. Once Google receives your password, it sends some kind of token to the email application, which remembers it. This is the same process for my IMAP mail on both desktop and Android.

So, no. That's incorrect Jan-Carlos.

[LonnieFry]

After about three days, my outgoing email on this account on this particular computer and in this particular email client started working again on its own. Since I did nothing in particular in between failures and success, I will chalk this up to a glitch that either Google fixed, or it was due to some kind of timeout value in the 2 or 3 day ballpark. Meanwhile, I had been using other clients for outbound email, all of which worked as normal.