Thunderbird won't connect to Gmail via OAuth2
I have two Gmail accounts. Both have IMAP enabled. The first can't be set up in Thunderbird with OAuth2 -- I need to enable "less secure apps" in my Google account, and then make manual settings. The second works as expected. What could be preventing the first account from connecting to TB? I had this issue on TB 68 and also on TB 78. If I remember correctly, I had this issue both on Windows and Linux. In the problematic Gmail account, I have both IMAP and POP enabled. Do I need to disable POP?
Chosen solution
So the solution is to install my root certificate BEFORE setting up any mail account. The reason my second account always worked was because by that time, I had installed the root certificate. My computer uses a corporate-style root certificate that monitors network traffic.
In any case, even without the root certificate, it would have worked, if I would have noticed that at the bottom of the manual configuration page, there is a box where you can manually select OAuth2.
Read this answer in context 👍 0All Replies (8)
You need to let go of that "less secure access". Google is getting rid of it and so should you. Turn it off and update/review your Google account's security. OAuth2 should work just fine for the affected account in Thunderbird. What exactly happens when you're setting up that account in Thunderbird? Which part of that setup isn't going through as expected? Give as much information as you can.
I can't configure that Gmail account unless I enable "less secure apps". If it is disabled, TB says it can't find the settings for my account. Even if I manually enter the proper settings, it is rejected, unless I enable "less secure apps". This holds true even if I disable POP support. It is a very old Gmail account, it was set up in 2005. The newer account works.
Modified by Shmu26
This is clearly not a Thunderbird problem, but an issue with that account. Review and update that account's security settings, like enabling modern authentication options like 2-factor authentication and generate an app specific password. This may force an update of that account on Google's servers and bring it up to spec for today's use. You may find better help here https://support.google.com/mail/ and here https://support.google.com/mail/community/
Thanks, I bet setting up 2-factor authentication would work, but since I have poor cell reception, and I don't like to schlep around a printed list of codes in my back pocket, and mark them off one by one, I will first try posting on the Google forum you linked me to. Maybe they can help?!
Don't you have a smartphone?
Not really, I can't connect my current phone to WIFI, but let's not get into that. I don't want to bore you. I will wait patiently :) to see what wisdom the Google forum has to share.
I never got an answer from google forum, but strangely, after switching to thunderbird flatpak, the OAuth2 started working.
Chosen Solution
So the solution is to install my root certificate BEFORE setting up any mail account. The reason my second account always worked was because by that time, I had installed the root certificate. My computer uses a corporate-style root certificate that monitors network traffic.
In any case, even without the root certificate, it would have worked, if I would have noticed that at the bottom of the manual configuration page, there is a box where you can manually select OAuth2.