can't create a gmail account (since gmail new version)
I had 2 gmail addresses in Thunderdbird. For the first one, I just changed the password authentication method to Oauth2 in the server parameters and it instantly made the replication work.
For the second one, I unfortunately deleted the account and couldn't recreate it, even with the "less secured application" set on in the Google Account parameters. I also tried to activate the 2 level connexion method and generate an application password but couldn't find any way to use it in thunderbird. Therefore, I'm stuck with Webmail Gmail application. I have noticed that the connection has been bllocked by Google (see image)
Hope some body can help (this is related to Google security reenforcement actions but seems that Thunderbird is not up to date on this issue).
Please find attached the first page of my troubleshooting info.
Chosen solution
Hi sfhomes, I made the change but still remains stuck.
I have read the very complete and interesting document linked in your message, review the Cookies setting in thunderbird, deleted the cookies from chrome, reconnected with chrome to my account ... No Change !
I have to say that I have a dozen of google accounts I work with. This might be a reason for the OAuth2 not working as it should. By the way, I also made some tries with the "less secured application authorization" set on in my google Account and "normal password" in Thunderbird. Not working either.
Finally, I had the idea to change the imap server name to "imap.googlemail.com" .... and the replication restarted immediatly !!
I tried to create a new Thdb account with an other gmail account (without "less secured apps" set on) using :
- imap.googlemail.com,
- OAuth2
... and it opened the google connection form to check the password and created the account !!
Conclusion : for any unknown reason the imap server should be googlemail instead of gmail (at least in France !).
PS : it took me one full testing day and a serious intuition to solve this issue.
Read this answer in context 👍 0All Replies (5)
Greetings,
You should try with less security level with your second email account, and contact the Gmail Support team.
I also need the page two of troubleshooting info, if it existing.
Ander.
Your gmail account 10 has the outgoing server authentication set to normal password, whereas the gmail account 29 outgoing server has OAuth2 authentication, the same as the incoming IMAP server. I suggest you make the incoming and outgoing servers both use OAuth2.
http://kb.mozillazine.org/Using_Gmail_with_Thunderbird_and_Mozilla_Suite
Chosen Solution
Hi sfhomes, I made the change but still remains stuck.
I have read the very complete and interesting document linked in your message, review the Cookies setting in thunderbird, deleted the cookies from chrome, reconnected with chrome to my account ... No Change !
I have to say that I have a dozen of google accounts I work with. This might be a reason for the OAuth2 not working as it should. By the way, I also made some tries with the "less secured application authorization" set on in my google Account and "normal password" in Thunderbird. Not working either.
Finally, I had the idea to change the imap server name to "imap.googlemail.com" .... and the replication restarted immediatly !!
I tried to create a new Thdb account with an other gmail account (without "less secured apps" set on) using :
- imap.googlemail.com,
- OAuth2
... and it opened the google connection form to check the password and created the account !!
Conclusion : for any unknown reason the imap server should be googlemail instead of gmail (at least in France !).
PS : it took me one full testing day and a serious intuition to solve this issue.
The kb article mentions in the first section:
"The account wizard might use googlemail.com instead of gmail.com in the server names. They are equivalent. Gmail was rebranded as Google Mail in Germany, Austria and the United Kingdom. Since 2012 Gmail is branded Gmail in germany".
Maybe France should be added to that list.
You are right. I have forwarded the info to Gmail support team. Could you have the KB article be updated ?