Can't change incorrect Gmail password
I have just installed Thunderbird v146.0, set up the first mail account (POP3) OK, then tried to set up a GMail IMAP account. I inadvertently gave it the wrong password, so the Account hub throws out the connection with an Authentication error "Unable to log in at server. Probably wrong configuration, username or password".
The problem is I can see no way of amending the password; if I try and set up the account again, it just skips the "enter password" step, presumably because TB thinks it already knows the password for this email account. I have tried the following:
- The "edit configuration" feature in the account hub doesn't have a change password option - The Saved Passwords section in Settings > Privacy & Security doesn't show the Gmail creds, presumably because it failed to set up this account in the first place - I reinstalled TB, having previously deleted the Profiles folder in C:\Users\<username>\AppData\Local\Thunderbird; everything I've read on this suggests this is the one and only place where TB keeps its data. However, when re-entering TB, the POP3 account I set up is still there, so there must be somewhere else that TB is storing its data, I guess the Registry?
Am I missing something? I can't be the only person who has had this problem!
Thanks
Valgt løsning
Final update: I discovered that if there is a service listening on port 80 (localhost) then this snaffles the authentication request. I have Apache running; disabling this and retrying solved the problem
Læs dette svar i sammenhæng 👍 0Alle svar (3)
the profile is at appdata\roaming, not appdata\local Try again
Thanks: right, there are profiles in both locations, it seems the Roaming one is the correct one. Deleting this successfully removes the orginal POP3 account; I have since discovered that deleting Google cookies forces a a new password reentry, so that takes care of that, but it's still not authenticating. For the record I can still access the Gmail account via Outlook and web. I have checked the incoming and outgoing server settings in Account hub and they seem correct, also OAuth2 is selected
Ændret af David H den
Valgt løsning
Final update: I discovered that if there is a service listening on port 80 (localhost) then this snaffles the authentication request. I have Apache running; disabling this and retrying solved the problem