[Users] [Bug 4601] New: gmail no longer supports "insecure" client

[Richard]

> Date: Sunday, June 19, 2022 11:32:46 -0300
> From: "J. Paul Bissonnette" <jpaulb at eastlink.ca>
>
> On Sun, 19 Jun 2022 14:10:03 +0100
> pete <petegn at mail.com> wrote:
> 
>> On Sun, 19 Jun 2022 18:00:58 +1000
>> Peter Richards <peter777 at users.sourceforge.net> wrote:
>> 
>> > On Sun, 19 Jun 2022 07:33:18 +0100
>> > Brad Rogers <brad at fineby.me.uk> wrote:
>> > 
>> > > Which is *exactly* why google make it so hard to use anything
>> > > else. Using an MUA (such as Claws) means they can't monitor
>> > > your every activity.
>> > 
>> > The following thread is marked "solved" and dated 2nd June 2022
>> > , so the date is after Google changed it all -
>> > https://www.aspsnippets.com/Articles/SOLVED-Gmail-server-denied-
>> > POP3-access-for-the-given-Username-and-Password.aspx
>> > 
>> > Has anyone tried the steps outlined in the thread ?
>> > 
>> 
>> Hi
>> 
>> Yes  tried
>> Total failure
> 
> complain here. If enough Claws Mail users leave Gmail they may
> revaluate their "secure" policy. I have notified everyone in my
> Gmail contact list that I will not be reachable there .
> https://support.google.com/accounts/contact/less_secure_apps

Do app passwords:
  
    <https://support.google.com/accounts/answer/185833?hl=en>

not work with gmail's POP3?

What google is trying to address is people using the same credentials
in various places - so making google accounts vulnerable when ones
credentials are stolen from some other site. While they would rather
that you use OAuth.2, their app password option, which works with
IMAP, also limits that exposure some.