On 16 May 2022 as I do recall,
Barry Punchard wrote:
> On 19 Apr
cvj...@waitrose.com wrote:
>
> >
> > There is a thread on the ROOL forum regarding Google withdrawing "Less
> > secure app" access. No firm conclusion seems to have been reached.
[snip]
> I know this has been discussed here and elsewhere and I have that same
> problem, using Messenger and Netfetch with a Google email account.
>
> What is the summary answer, please? Google are still pushing this as something
> they will do imminently - like in a few weeks. So is this something a
> change in RISCOS/ RComp software is planning to deal with?
>
> a) If so, can we expect modified software to be made available soon?
>
> b) Or, has a step by step alternative been produced?
>
Chris Newman posted a step-by-step alternative in
comp.sys.acorn.networking. It requires one-off web access to GMail (so
won't work with NetSurf) and one-off access to a mobile phone, but after
that you can continue to access your e-mail via Netfetch and POP3.
---------- Begin forwarded message ----------
Date: Mon, 09 May 2022 00:20:12 +0100
From: Chris Newman <
cvj...@waitrose.com>
Newsgroups: comp.sys.acorn.networking
Subject: Re: Google and the end of May
In article <
6da978e15...@bazleyfamily.co.uk>, Harriet Bazley
<
har...@bazleyfamily.co.uk> wrote:
> On 30 Apr 2022 as I do recall, Chris Newman wrote:
> [snip]
> > As I understand it, if you wish to keep accessing Google on older
> > (Less secure?) kit you will need to get a new password to put in to
> > your mail transport prog. This only needs to be done once unless you
> > have some sort of catastrophic failure of your set up. Presumably
> > even then, if you've saved it, you can re-insert. You can still log
> > in online with your original password. Then each time you connect
> > with said older kit, you will have to get a 2 factor code from them.
> > Whether that arrives by phone, mail or what I know not.
> Ouch. So *every single time* your mail transport tries to fetch from
> your inbox, you will have to manually confirm your identity... i.e.
> every twenty minutes or so?
Seemingly, its not as bad as I thought. You won't need to confirm every
time.
Thanks to an article in Computer Active magazine, I've sorted the first
of my Google accounts.
I've tried to make an idiot's guide. Herewith....
2 factor authentication for "insecure" apps.
Sign into your Google account.
Select "Security" in the left hand menu.
You may have to keep signing back into you account to verify it's you
during the process.
Follow instructions to enable 2-step verification.
You will need a phone for the set up as they send you a code. I had one
listed with them as I have an Android phone which needs the ridiculously
named "PlayStore."
You can ignore the bits about further safety measures.
Go back to "Security" page.
With a bit of searching you should see a new option "App Passwords"
Select "Mail" in the "Select App" drop down menu no matter what
app/client/transport you are using.
In the "Select device" menu, choose the device you want to access gmail
on. I chose other and when asked, called it Hermes.
Select "Generate" to get you 16 digit password which appears in a
yellowish box.
Enter this in your email/transport client in place of you old code.
You should only have to do this once but keep a copy of the code in case
of disasters. If the worst comes to the worst, you can get Google to
generate a new one.
You may have to do a capcha or get another code. I was so confused, I
slightly disremember the order of events.
Then all should work.
When I accessed my Google account on-line it was my original password
that was needed. I had to get a code to log in the first time but there
is a "Don't ask again on this device" box to tick to prevent that each
time you login in future.
How does it know my device? IP address, MAC address?
--
Chris Newman
----------- End forwarded message -----------
--
Harriet Bazley == Loyaulte me lie ==
The way to a man's heart is through the left ventricle.