<html><head></head><body><div class="ydp88de4c49yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false">I got that message over a month ago, maybe two months. I have Claws Mail in Linux, and it was affected. I had to enable 2-Factor Authentication. This means I have to use my smart phone to log into gmail now. I also had to obtain and enter into my gmail profile the app password for Claws Mail, which was generated from my Google Account. I simply entered the app password into the account profile and checked off Save Password. So I no longer have to enter my password each time I download gmail into Claws. Actually this is more convenient than the old two-step way. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Fastmail (paid email service based in Australia) imposed the app password scheme (but not 2FA) over a year ago. Same setup. If I want to use Thunderbird, it gets its own App Password, or else I can use OAuth if I choose to learn how to set that up. Yahoo and Google both use versions of OAuth if you want to go that route. Yahoo has also been requiring an App Password for months if not over a year now. But not 2FA. So only my Google Account uses 2FA in addition to App Passwords right now. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">My phone logs into Google through Android, meaning that the only password used in the PIN by which I unlock the phone. This strikes me as less secure than even an App Password, but that's the way they do things in Android. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Comcast has a different scheme, which involves a couple of server redirects. Somehow, this is supposed to be more secure than the more direct logins they used to use. They still allow user name and password to log in through my email clients. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">IMAP and POP3 seem to use the same schemes with the services I have mentioned. POP3 is said to be less secure than IMAP, so it may someday be going away. I'll have to expand my Local Folders when and if this happens. (This allows making changes or moving messages or deleting messages on one device without affecting the originating server or the other devices. The very antithesis of sync.) </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">The times they are a-changin'. You've got to roll with the changes. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">-- Bob Primak </div><div dir="ltr" data-setdir="false"><br></div>
</div><div id="yahoo_quoted_4673126777" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Saturday, June 4, 2022, 12:12:08 AM EDT, Drew King <dking65@kingconsulting.us> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv7219577386">
<div>
<p><font size="4">All,</font></p>
<p><font size="4">Anyone get struck down while using
old/outdated/unsupported apps while connecting to Google?
Typically, very old versions of MS Outlook fit the bill. Anyone
still use Outlook 2007? Wondering if it still works. My Outlook
2010 client can still access Gmail.<br>
</font></p>
<p><font size="4">Google does let you use special "Application
Passwords". A unique password for each application.<br>
</font></p>
<p><font size="4">This is a snip from a Google message I received.
Google was reminding me that I use application passwords, which
it also discourages.</font></p>
<p><font size="4">Mozilla Thunderbird supports the newer Google
authentication, OAuth2. OAuth 2.0 is the industry-standard
protocol for authorization.<br>
</font></p>
<p><img src="cid:mpKbRQ7ivaInGQlyyC5B" yahoo_partid="1.2.2" alt="" width="927" height="483" class="yiv7219577386"></p>
<p><br>
</p>
<div class="yiv7219577386moz-signature">-- <br>
Drew King <br>
<br>
<br>
</div>
</div>
</div>===============================================<br>::The Lexington Computer and Technology Group Mailing List::<br>Reply goes to sender only; Reply All to send to list.<br>Send to the list: <a ymailto="mailto:LCTG@lists.toku.us" href="mailto:LCTG@lists.toku.us">LCTG@lists.toku.us</a> Message archives: <a href="http://lists.toku.us/private.cgi/lctg-toku.us" target="_blank">http://lists.toku.us/private.cgi/lctg-toku.us</a><br>To subscribe: email <a ymailto="mailto:lctg-subscribe@toku.us" href="mailto:lctg-subscribe@toku.us">lctg-subscribe@toku.us</a> To unsubscribe: email <a ymailto="mailto:lctg-unsubscribe@toku.us" href="mailto:lctg-unsubscribe@toku.us">lctg-unsubscribe@toku.us</a><br>Future and Past meeting information: <a href="http://LCTG.toku.us" target="_blank">http://LCTG.toku.us</a><br>List information: <a href="http://lists.toku.us/listinfo.cgi/lctg-toku.us" target="_blank">http://lists.toku.us/listinfo.cgi/lctg-toku.us</a><br>This message was sent to <a ymailto="mailto:bobprimak@yahoo.com." href="mailto:bobprimak@yahoo.com.">bobprimak@yahoo.com.</a><br>Set your list options: <a href="http://lists.toku.us/options.cgi/lctg-toku.us/bobprimak@yahoo.com" target="_blank">http://lists.toku.us/options.cgi/lctg-toku.us/bobprimak@yahoo.com</a></div>
</div>
</div></body></html>