Avatar for Username

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

Wo archive tread sia. Meɖekuku bia biabia yeye ne ehia kpeɖeŋu.

Unable to login to IMAP Gmail account on Thunderbird 38.5.0

  • 1 ŋuɖoɖo
  • 1 masɔmasɔ sia le esi
  • 1 view
  • Nuɖoɖo mlɔetɔ sfhowes

nearly.normal.ashish
nearly.normal.ashish
more options

I have 7 different work emails configured on TB. All of these are essentially gmail/ google for work accounts.

Since the recent Google outage 2-3 days ago one of these accounts will not connect. Every time i try to fetch emails for this particular account I would be redirected to the gmail sign in page. Once I enter my password nothing happens.

The other email accounts seem to be working fine.

Assuming there must be some data corruption I have tried the following so far.

1. Deleted saved passwords from TB. - Did not work.

Now another email account setup with Imap asks me for my password everytime I launch TB. At least it logs in without errors. The original problem was no resolved.

2. I allowed access to less secure apps from the gmail web interface - no use.

3. Removed the problematic email account from TB and tried to re-add. - Did not work.

After entering the email address, password, and TB fetching the gmail server details (IMAP & SMTP) it would connect to the gmail login page for oAuth2 authentication. On entering the user name and password, i return to the setup screen showing "sending password". It basically stalls here.

4. Uninstalled TB and removed Profile folder and reinstalled TB. It still stalls at the sames point as in 3. above.

5. I have tried installing TB on another machine and tried to setup my email account there. It worked without a glitch.

So my conclusion is that there is some old account details stored on my work machine which does not get deleted when I am uninstalling TB.

I am currently using TB 38.5.0 on a windows server 2003 (SP2?). I have been using TB on the same machine for over 5 years.

Any suggestions guy?

I have 7 different work emails configured on TB. All of these are essentially gmail/ google for work accounts. Since the recent Google outage 2-3 days ago one of these accounts will not connect. Every time i try to fetch emails for this particular account I would be redirected to the gmail sign in page. Once I enter my password nothing happens. The other email accounts seem to be working fine. Assuming there must be some data corruption I have tried the following so far. 1. Deleted saved passwords from TB. - Did not work. Now another email account setup with Imap asks me for my password everytime I launch TB. At least it logs in without errors. The original problem was no resolved. 2. I allowed access to less secure apps from the gmail web interface - no use. 3. Removed the problematic email account from TB and tried to re-add. - Did not work. After entering the email address, password, and TB fetching the gmail server details (IMAP & SMTP) it would connect to the gmail login page for oAuth2 authentication. On entering the user name and password, i return to the setup screen showing "sending password". It basically stalls here. 4. Uninstalled TB and removed Profile folder and reinstalled TB. It still stalls at the sames point as in 3. above. 5. I have tried installing TB on another machine and tried to setup my email account there. It worked without a glitch. So my conclusion is that there is some old account details stored on my work machine which does not get deleted when I am uninstalling TB. I am currently using TB 38.5.0 on a windows server 2003 (SP2?). I have been using TB on the same machine for over 5 years. Any suggestions guy?

Ŋuɖoɖo si wotia

If the version of TB that was installed on the other computer that worked without a glitch was 78, that is because several fixes to gmail's OAuth2 were applied in version 60+. With TB 38, I wouldn't expect OAuth2 to work, only normal password.

Since the recent outage, one fix is to remove TB from the allowed apps in the Google account security settings, then reconnect and enter the password. For OAuth2, cookies must be enabled in TB Privacy settings.

Xle ŋuɖoɖo sia le goya me 👍 0

All Replies (1)

sfhowes
sfhowes
  • Top 10 Contributor
more options

Ɖɔɖɔɖo si wotia

If the version of TB that was installed on the other computer that worked without a glitch was 78, that is because several fixes to gmail's OAuth2 were applied in version 60+. With TB 38, I wouldn't expect OAuth2 to work, only normal password.

Since the recent outage, one fix is to remove TB from the allowed apps in the Google account security settings, then reconnect and enter the password. For OAuth2, cookies must be enabled in TB Privacy settings.