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

OAuth2 authentication for Gmail never finishes; it just runs for hours with no error message. (Mac computer, TB 38)

more options

Hi everyone,

I recently downloaded a version of Thunderbird 38 for use on an older Mac (older than the one I’m using to create this post). Now, I’m trying to set up OAuth2 to comply with Google’s new requirements for Gmail, but the final steps (authentication, generation of an OAuth2 token) never finish. This is what I’ve done so far:

The Gmail account that I want to set up with OAuth2 is set to IMAP for incoming (I had to create a new account in Thunderbird for this) and SMTP for outgoing. OAuth2 is selected in TB for both servers. The Google login window pops up, and I can enter my information and click “Allow” for TB to access my Google Account. After that, though, the process just runs. There’s a blue circle near the top left corner of the TB window (next to the word “Inbox”) that keeps spinning, and a line of diagonal blue stripes in a small graphic at the bottom of the window keeps moving to the right, but nothing else happens. This will go on for hours if I let it. I can take other actions in TB (change settings, etc.) while this is going on, and no error message ever appears.

I should also note that I get alerts from Google (which I can access via other devices) about a new sign-in, and the computer in question shows up in my Google Account screens as being signed into my account. I have also recognized the new sign-ins by clicking the “Yes, it was me” button. Therefore, it appears that TB has successfully connected to my Google Account; I just don’t know why the authentication won’t complete itself. Should I let it run, even with the understanding that it might take several hours?

Here are some further details, based on what I’ve read while doing research on my own:

-Cookies are enabled in TB (“Accept always,” “Keep until they expire”). -Two Google-based cookies have appeared (google.com, accounts.google.com). -My computer’s firewall is off for the time being. I don’t have any antivirus software, as this is a Mac. -My “User Name” in the Server Settings window is my full e-mail address. -There is nothing written in the “Saved Passwords” window. -I’ve tried shutting my computer down entirely and then restarting the authentication process. -I don’t think my computer can run any versions of TB that are later than 38. -Specific incoming/outgoing settings: IMAP port 993, SSL/TLS, OAuth2 for incoming; SMTP port 587, STARTTLS, OAuth2 for outgoing.

I really need to access my Gmail on this computer, but am not a tech person and have run out of ideas to try on my own. Any help would be *greatly* appreciated! And, of course, I’d be happy to provide additional details if necessary.

Thank you!!

P.S. If it would be simpler to use my original POP account with 2-factor authentication, then I would be open to doing that instead. I just haven’t been able to find out if “app passwords” are compatible with TB 38.

Hi everyone, I recently downloaded a version of Thunderbird 38 for use on an older Mac (older than the one I’m using to create this post). Now, I’m trying to set up OAuth2 to comply with Google’s new requirements for Gmail, but the final steps (authentication, generation of an OAuth2 token) never finish. This is what I’ve done so far: The Gmail account that I want to set up with OAuth2 is set to IMAP for incoming (I had to create a new account in Thunderbird for this) and SMTP for outgoing. OAuth2 is selected in TB for both servers. The Google login window pops up, and I can enter my information and click “Allow” for TB to access my Google Account. After that, though, the process just runs. There’s a blue circle near the top left corner of the TB window (next to the word “Inbox”) that keeps spinning, and a line of diagonal blue stripes in a small graphic at the bottom of the window keeps moving to the right, but nothing else happens. This will go on for hours if I let it. I can take other actions in TB (change settings, etc.) while this is going on, and no error message ever appears. I should also note that I get alerts from Google (which I can access via other devices) about a new sign-in, and the computer in question shows up in my Google Account screens as being signed into my account. I have also recognized the new sign-ins by clicking the “Yes, it was me” button. Therefore, it appears that TB has successfully connected to my Google Account; I just don’t know why the authentication won’t complete itself. Should I let it run, even with the understanding that it might take several hours? Here are some further details, based on what I’ve read while doing research on my own: -Cookies are enabled in TB (“Accept always,” “Keep until they expire”). -Two Google-based cookies have appeared (google.com, accounts.google.com). -My computer’s firewall is off for the time being. I don’t have any antivirus software, as this is a Mac. -My “User Name” in the Server Settings window is my full e-mail address. -There is nothing written in the “Saved Passwords” window. -I’ve tried shutting my computer down entirely and then restarting the authentication process. -I don’t think my computer can run any versions of TB that are later than 38. -Specific incoming/outgoing settings: IMAP port 993, SSL/TLS, OAuth2 for incoming; SMTP port 587, STARTTLS, OAuth2 for outgoing. I really need to access my Gmail on this computer, but am not a tech person and have run out of ideas to try on my own. Any help would be *greatly* appreciated! And, of course, I’d be happy to provide additional details if necessary. Thank you!! P.S. If it would be simpler to use my original POP account with 2-factor authentication, then I would be open to doing that instead. I just haven’t been able to find out if “app passwords” are compatible with TB 38.

Chosen solution

app passwords are generally compatible with basically anything. I would assume is should work with V38. But it will cost nothing to try it and it is only in trying it you will know if it works. I don't know and google are unlikely to tell you.

Issues I am aware of.

V38 https://bugzilla.mozilla.org/show_bug.cgi?id=1176773 and https://bugzilla.mozilla.org/show_bug.cgi?id=1178413

Both appear to be fixed in June, so you probably need a version released after that.

There is also the common issue of the authentication flow using localhost. So if you have something else like a web or FTP server monitoring and consuming packets. That will break things. Apache keeps coming up.

Read this answer in context 👍 0

All Replies (2)

more options

Chosen Solution

app passwords are generally compatible with basically anything. I would assume is should work with V38. But it will cost nothing to try it and it is only in trying it you will know if it works. I don't know and google are unlikely to tell you.

Issues I am aware of.

V38 https://bugzilla.mozilla.org/show_bug.cgi?id=1176773 and https://bugzilla.mozilla.org/show_bug.cgi?id=1178413

Both appear to be fixed in June, so you probably need a version released after that.

There is also the common issue of the authentication flow using localhost. So if you have something else like a web or FTP server monitoring and consuming packets. That will break things. Apache keeps coming up.

more options

Hello Matt,

Thank you for your quick reply! My setup is very simple, so I doubt there are other programs or servers interfering with the OAuth2 process. If anything, there might be some deep-rooted compatibility issues that would be difficult to diagnose/fix, so I went the other route with 2FA.

App passwords do indeed work with Thunderbird 38. Although the information pages in Google’s Help Center say that an app password has to be entered only once, I was prompted again on subsequent sign-in attempts. However, I saved the password in Password Manager for both incoming and outgoing, and all seems to be well.

Thanks again! I appreciate your help and will mark your post as having solved the problem.