Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Instaled Thunderbird to pick up gmail using POP, but get message Sending of password for user ****@gmail.com did not succeed. password not accepted.

  • 9 wótegrona
  • 3 maju toś ten problem
  • 3 naglědy
  • Slědne wótegrono wót Brian

more options

Just installed latest version of Thunderbird on a new PC running Windows 10 to pick up emails from gmail account. Set up for POP, but get message - "Sending of password for user ***@gmail.com did not succeed. Mail server pop.gmail.com responded: Username and password not accepted." Password is correct, as i can log into gmail using website. I can send emails using this account from Thunderbird. I deleted account and set up for IMAP, and all works fine. Removed IMAP to set up POP again, and get the same error message, all server settings are correct according to gmail.

Just installed latest version of Thunderbird on a new PC running Windows 10 to pick up emails from gmail account. Set up for POP, but get message - "Sending of password for user ***@gmail.com did not succeed. Mail server pop.gmail.com responded: Username and password not accepted." Password is correct, as i can log into gmail using website. I can send emails using this account from Thunderbird. I deleted account and set up for IMAP, and all works fine. Removed IMAP to set up POP again, and get the same error message, all server settings are correct according to gmail.

Wubrane rozwězanje

Yes, go to google and turn the less secure apps setting on.

https://myaccount.google.com/lesssecureapps?pli=1

IMAP uses oAuth for authentication, pop does not (at least for another few weeks) to needs to have the less secure apps setting turned on.

The next point release should fix that issue in a few weeks.

Toś to wótegrono w konteksće cytaś 👍 2

Wšykne wótegrona (9)

more options

Wubrane rozwězanje

Yes, go to google and turn the less secure apps setting on.

https://myaccount.google.com/lesssecureapps?pli=1

IMAP uses oAuth for authentication, pop does not (at least for another few weeks) to needs to have the less secure apps setting turned on.

The next point release should fix that issue in a few weeks.

more options

Hi Matt,

Many thanks, that has sorted the problem.

Kes

more options

Revisit the authentication method used when 68.5 lands. It will have oauth for pop accounts and will make your life with gmail much easier in the long run. They are pushing oauth hard and helpfully turn less secure app off when they do security checks with you, so unless you are really on the ball your mail suddenly stops working..

more options

Many Thanks Mat, i will keep my eye out for 68.5. I know what to look for and what to do next time.

Thanks again,

Kes

more options

Hi Matt - any other suggestions for resolving this problem? Changing settings in GMail/Google to accepting less secure apps hasn't worked for me.

This past Monday, for no clear reason, TB 68.5 (Win 10) just stopped accepting current password for 1 GMail POP account.

Look forward to hearing your advice.

Tks Chris

more options

Change the authentication to OAuth2 in Server Settings for the incoming server and also in Outgoing Server (SMTP), in Tools/Account Settings. Remove the passwords in Tools/Options/Security/Passwords/Saved Passwords, restart TB, and enter the regular account password in the OAuth2 browser window when prompted. Cookies must be enabled in TB Tools/Options/Privacy.

more options

crideout.trg said

Hi Matt - any other suggestions for resolving this problem? Changing settings in GMail/Google to accepting less secure apps hasn't worked for me. This past Monday, for no clear reason, TB 68.5 (Win 10) just stopped accepting current password for 1 GMail POP account. Look forward to hearing your advice. Tks Chris

sfhowes said

Change the authentication to OAuth2 in Server Settings for the incoming server and also in Outgoing Server (SMTP), in Tools/Account Settings. Remove the passwords in Tools/Options/Security/Passwords/Saved Passwords, restart TB, and enter the regular account password in the OAuth2 browser window when prompted. Cookies must be enabled in TB Tools/Options/Privacy.

Did that work for you Chris

more options

Yes, thank you - easy to follow instructions, made process feel uncomplicated and seamless to incorporate into security settings.

more options

Thanks, that worked fine! Of course, immediate triggered a Google 'Critical security alert'  :-)