After all, that’s what Google is going to do after May 30th…disable less secure account access by default.
POP3 GMAIL ACCOUNT IN OUTLOOK 2013 HOW TO
I’m sure that if one performs a search using a search such as “oauth2 on Outlook 2019” that there should then be results showing just how to implement it within Outlook, after which one’s Google account can then be changed from allowing less secure apps to disallowing them. I use Thunderbird, so I went looking for advice on how to enable OAuth 2 in it and found a site that had great directions on how to do so. In looking at various Google help pages yesterday, I noted one page that said that Outlook 2016 does not support OAuth 2.0, but Outlook 2019 does, or at least that’s what the page on Google claimed. I added the bolding above to highlight the key to proceeding…use OAuth 2 and you might be all set. …Instead, you’ll need to sign in using Sign in with Google or other more secure technologies, like OAuth 2.0. I keyed in on one thing mentioned in the body of the email for my clue on how to proceed: I got one of those emails a few days ago as well, and was able to make a couple of changes within my email client to be able to keep going with gmail and my email client. But this is a one time effort and we are never again prompted for passwords when we run Outlook. Sometimes we had to wait a couple of days to retry.
POP3 GMAIL ACCOUNT IN OUTLOOK 2013 PASSWORD
All our GMail accounts currently use a version of Outlook with App Passwords.įirst time setup with an App Password is sometimes a pain, but it has eventually worked for us with IMAP and POP3. These don’t appear affected by the policy change. For this use case, Google has 16 character application passwords. īut when using an application such as an Outlook with IMAP or POP3 that lacks 2FA support, you are stuck and don’t want to constantly have a 2FA exchange every time you download your email. When 2FA is on, the “less secure app” setting is automatically disabled. We already use 2FA for all our GMail accounts. After reading joep517’s first link ( ), my expectation is we won’t be affected.
0 kommentar(er)
