Re: OT - Google accounts turning off less secure access

Just checked a Gmail a/c in

Ahem, also true with AdBlockPlus /disabled/

The app-specific password I did with gmail last week seems to be working fine here.

Ah, then its pop mail that is an insecure app. Or summat. I dunno. They just kept barfing at me till I 'fixed' it.

In article snipped-for-privacy@mid.individual.net>, Tim Streater snipped-for-privacy@greenbee.net writes

How do you get such a password?

First you need to enable two-step verification

Then you can create app-specific passwords, but you can't turn off 2SV, or the app-specific passwords will be deleted

Are you also using turnpike for email? If not then enabling oAuth2 in your email client may well be less disruptive ...

The following is from a note I will be sending to users of my app:

What I have found is that one can continue with the existing app by using something called an app-specific password. I'm doing this and it seems to work. Here's how.

Firstly, you'll need to logon to your gmail account, and under "Manage account", choose "Security". Then, choose to enable Two-step-verification, or

Having done this, return to your Security page, and in the part on "Signing in to Google", you'll see the section about "App Passwords". Expand that section next. Where you see "Select device" in that section, choose your device type. Then, where it says "Select App", choose "Other" and enter the name of your email client. Now you can click "Generate". This will put up a pane with a password in large type that you need to copy (with ctrl/cmd-c or similar) to the clipboard.

Now switch to your email client and open the Preferences. Choose your gmail account, highlight the password field, and paste (with ctrl/cmd-v or similar) the password you copied above into the password field. Then click Save.

End of.

Thanks for that and yes I am still using TP for email.

In article snipped-for-privacy@mid.individual.net>, Tim Streater snipped-for-privacy@greenbee.net writes

Thanks

Tim Streater snipped-for-privacy@greenbee.net posted

Yes, that seems to have worked for me without having to bother with OAuth2 etc.

Blocked from gmail access today , presumably about 12:00 GMT today, no explanation returned other than "enter new password"

Did you not read my post about what you need to do, from a few days ago?

Normal gmail service returned by the evening. Your previous info saved but not acted on yet. I observe the principle, If it aint broke , don't fix it, ; as often other problems emerge when updating/altering/reconfiguring something that was otherwise working normally.

I've seen the same thing. Windows Live Mail gave a bad password response (popup for POP username/password) yesterday. I didn't get round to checking my Gmail mailbox via webmail until this morning. I then confirmed that Thunderbird and the Samsung "Mail" app on my Android phone both worked because they were already configured to use OAuth2. I was all set to have to working out how to turn on 2FA so I could define an app-specific password for WLM, but when I checked for mail just now, it received recent messages.

I too am inclined leave well alone - if it continues to work, all well and good. If it starts failing permanently, then I'll either set up Thunderbird on my PC, just for the GMail account, or else I'll look into 2FA and app-specific password.

I really would like to continue using WLM if I can, but Thunderbird is a possibility, assuming there is a way of importing saved mail from WLM.

It's a shame that MS abandoned WLM, and their only solutions are the Win 10 "Mail" app (which is nobbut a toy!) or Outlook (which is a pain to configure and test, doesn't allow you to export mail settings to .iaf files once you've got everything setup, and saves all your mail to one humungous .pst file which needs to be backed up entirely, unlike WLM where you are only saving new/changed/deleted messages so there's much less to backup. Thunderbird is like Outlook Express: you backup individual mail folders, so it's a half-way house between WLM and Outlook.

Well obvs, if your email client has implemented OAuth2, then there's nothing you need do except ensure it's used for gmail. Those clients that haven't, or as in my case won't, implement that can use the procedure I outlined.

In article snipped-for-privacy@mid.individual.net>, Tim Streater snipped-for-privacy@greenbee.net writes

Day 3 and my set up, unchanged, is still working.

Well bully for you. So your point was *what*, precisely?

In article snipped-for-privacy@mid.individual.net>, Tim Streater snipped-for-privacy@greenbee.net writes

Nothing really. Just saying. Maybe UK servers will be changed after bank holiday but it should have stopped working as of 301st May should it not.

It changed for me on the 30th, old logins no longer work, oauth2 still works, seems they are doing it as a phased change, based in god-knows what order.