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

Need help to debug imap authentication failure with gmail.

  • 27 replies
  • 4 have this problem
  • 368 views
  • Last reply by mozilla113

more options

I seem to be experiencing an issue similar to here:

https://support.google.com/mail/thread/4528103?msgid=19227686

Only in my case none of the workarounds seem to fix it. I was already using an app password and yesterday (2019-12-03) it suddenly stopped. Regenerating the app pass word doesn't help and neither does switching to oauth2. When I try oauth2 I get all the right login screens and I get the google validation but thunderbird sees some sort of failure. When I use app password I just get that the password is incorrect and to retry.

I'm using TB 68.2.1 on Ubuntu LTS 18.04.3

How can I get more debugging information on what might be happening?

Thanks.

All Replies (7)

more options

For the non-working account, delete the passwords and/or oauth tokens from Edit/Preferences/Security/Passwords, restart TB, and enter the regular account password in the OAuth browser window (assuming you're using OAuth authentication). Before that, confirm the password by logging in on the gmail website.

more options

I did that just now, no change.

I also completely deleted the non-working account, rebooted the laptop, to clear everything I was hoping, and I continue to get the imap error. Only in this account, all else is okay.

more options

I am having similar trouble setting up imap retrieval from gmail. I have tried with both normal password and oauth2. Running TB 68.6.0 on freebsd 11.3-RELEASE. When it attempts to fetch mail, Google pops up a window asking for authorization (window looks like a restricted (no toolbar) browser window with TB icon in upper left). However, if I enter the account and click the next button, it simply redisplays the request for the account. The behavior is the same one might see running firefox with noscript when a site is disabled -- it's as if nothing was entered into the box. If I start up firefox and go to accounts.google.com I can login just fine. The orginization has less secure logins disabled. I have password saving disabled.

more options

mozilla113 said

I am having similar trouble setting up imap retrieval from gmail. I have tried with both normal password and oauth2. Running TB 68.6.0 on freebsd 11.3-RELEASE. When it attempts to fetch mail, Google pops up a window asking for authorization (window looks like a restricted (no toolbar) browser window with TB icon in upper left). However, if I enter the account and click the next button, it simply redisplays the request for the account. The behavior is the same one might see running firefox with noscript when a site is disabled -- it's as if nothing was entered into the box. If I start up firefox and go to accounts.google.com I can login just fine. The orginization has less secure logins disabled. I have password saving disabled.

Do you have cookies enabled in TB Edit/Preferences/Privacy? They're needed for accounts.google.com to complete the OAuth process. With OAuth2, it's not necessary to enable 'less-secure aps'. Delete any passwords or tokens in Edit/Preferences/Security/Passwords/Saved Passwords, restart TB, and enter the account password in the OAuth window when prompted.

more options

Cookies were not enabled in TB, thanks. I got the login process to proceed to the point of getting the display saying this will allow TB to access all my gmail stuff, to which I said yes. But then nothing was downloaded, and now it just says login failed (window in upper right corner of TB) whenever it attempts to download. download.mozilla.org is the only cookie stored, which seems strange at this point. Cookies are set to keep until they expire. Accept third-party cookies is set to Always, although it seems like it should be ok to set it to Never.

more options

A little more info. In my gmail account, there is a security alert that says TB was given account access. However, when TB attempts to fetch mail, I get an authentication failure. Since it doesn't ask for a new password, there's no way to insure/check that the pw is correct. The security summary for my account at gmail does not show a failed sign-on attempt, although I don't know if it would in this circumstance.

more options

I finally got it to work. I had unchecked the "remember password" box, as I prefer to force myself to type in the pw as a memory aid. I *think* the problem was the password has to be remembered.

  1. 1
  2. 2