搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

gmail security and thunderbrid 38.2

  • 5 个回答
  • 10 人有此问题
  • 3 次查看
  • 最后回复者为 mmmmpppp1

more options

I had to set my gmail account on Google to allow less secure apps to be able to enter my PW when getting mail on Thunderbird. This doesn't make sense to lower security just to use the Thunderbird app. Needs fixing or I am doing something wrong.

I had to set my gmail account on Google to allow less secure apps to be able to enter my PW when getting mail on Thunderbird. This doesn't make sense to lower security just to use the Thunderbird app. Needs fixing or I am doing something wrong.

被采纳的解决方案

Thunderbird supports OAuth2 authentication for Gmail for IMAP accounts. OAuth2 is what Google considers to be 'safe'. OAuth2 isn't available for POP accounts. That doesn't mean Thunderbird is 'insecure'. In any case, turning on 2-step authentication significantly increases security for your Google account, regardless of whether you use OAuth2 or not. With 2-step authentication you don't have to allow 'less secure apps'. See this topic for more information. https://support.mozilla.org/en-US/questions/1083852

定位到答案原位置 👍 3

所有回复 (5)

more options

What is your account type - POP or IMAP?

more options

my Thunderbird is pop.

more options

选择的解决方案

Thunderbird supports OAuth2 authentication for Gmail for IMAP accounts. OAuth2 is what Google considers to be 'safe'. OAuth2 isn't available for POP accounts. That doesn't mean Thunderbird is 'insecure'. In any case, turning on 2-step authentication significantly increases security for your Google account, regardless of whether you use OAuth2 or not. With 2-step authentication you don't have to allow 'less secure apps'. See this topic for more information. https://support.mozilla.org/en-US/questions/1083852

more options

Thank you. I switched to OAuth2 and I can log in to my gmail account now.

more options

I changed to Oauth2, and it fixed my problem too. But several weeks later the problem is happening again with Oauth2 set!