Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

After updated to 68.10.0 (32-bit), Thunderbirds no longer able to login my Gmail

  • 2 ответа
  • 1 имеет эту проблему
  • 1 просмотр
  • Последний ответ от xiaogangz

more options

I used Thunderbird for many years without a serious problem. But today, after followed Thunderbird's promote to updated it to 68.10.0, I am no longer able to login to my gmail account from Thunderbird. It always gives the message "Sending of password for user xxx@gmail.com did not succeed. Mail server pop.gmail.com responded: Web login required: https://support.google.com/mail/answer/78754".

When I login for web browser to my gmail account, I cannot find anything wrong. The "less secure app access" is ON, "2-step verification" is not used. So, what else I can do, or is it a bug of 68.10.0?

Please help, thank you in advance.

Xiaogang

I used Thunderbird for many years without a serious problem. But today, after followed Thunderbird's promote to updated it to 68.10.0, I am no longer able to login to my gmail account from Thunderbird. It always gives the message "Sending of password for user xxx@gmail.com did not succeed. Mail server pop.gmail.com responded: Web login required: https://support.google.com/mail/answer/78754". When I login for web browser to my gmail account, I cannot find anything wrong. The "less secure app access" is ON, "2-step verification" is not used. So, what else I can do, or is it a bug of 68.10.0? Please help, thank you in advance. Xiaogang

Все ответы (2)

more options

Have you tried actually using the unlock capatcha mentioned in the support article you link to https://accounts.google.com/b/0/DisplayUnlockCaptcha

That is the usual solution.

For a longer lasting result make sure all gmail accounts are accessed with oAuth authentication. Note that oAuth requires cookies be enabled.

more options

Thanks Matt, I have just tried, but the problem still remains the same.