Thunderbird set gmail imap account, always pop-up enter password agian
We have 8 co-worker set up same gmail imap account in thunderbird. It have a strange problem, the thunderbird always pop-up authentication is wrong and need enter the password again. Sometimes we re-enter is work and recieve again, sometimes can't and it will keep to pop-up need enter password. But if we only 2or 3 user open the thunderbird to use, it won't appear this problem. What can i do can fix this case, we can't only 2 or 3 user do the job, another can't do anythings. Also i was check gmail informtaion, it said that "A single account can only use up to 15 IMAP connections" , but we just only 8 people.
All Replies (3)
Right click the account in the folder pane and select settings. In server settings for the account click the advanced button and set the maximum number of connections to use to 1. Expect it to be slow with the reduced connections.
Make sure no one uses a phone as well, as that would make you 16 people. Make sure no one uses an apple device. Their mail products to not have the ability to throttle connections at all.
I suggest you consider another long term plan as having 8 people accessing the same mail account in not a good long term strategy. It will fail, or at least be fragile.
I want to know if i change my authentication to "Oauth2", this setting will more stable or not?
And what is the different between "Oauth2" and "normal password"
infinity-ray said
I want to know if i change my authentication to "Oauth2", this setting will more stable or not?
It is Googles preferred authentication mechanism and will mean you don't need to have less secure apps on, so you stop getting the idiot notices from Google telling you you are making things insecure. Is it more stable? I have no idea I have used both Normal password and oAuth with google and see no issues at all with either method. Others have no end of troubles with oAuth, but that in every case I have followed been caused by anti virus products and modified settings on cookies and cache.
And what is the different between "Oauth2" and "normal password"
That is well beyond my ability to explain. A normal password is just that, a password provided when it is asked for. OAuth uses a challenge response process and authorization tokens. Beyond that I really do not know. There is a standard that describes it here https://tools.ietf.org/html/rfc6749 But be advised there is a standard for 4G mobile/Cell data as well. I use it, but I do not profess to understand it either.