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

[cr]

On Fri, 3 Jun 2022 18:17:43 +1200
cr <cr at orcon.net.nz> wrote:

> On Fri, 3 Jun 2022 08:46:16 +0300
> Nick Koretsky <nick_koretsky at ukr.net> wrote:
> 
> > On Fri, 3 Jun 2022 14:14:48 +1200
> > cr <cr at orcon.net.nz> wrote:
> > 
> > > 
> > > > To add to what Geoffrey says:
> > > > google shutting out CM is NOT a bug in CM. It's a policy
> > > > decision.  By google.  There's *nothing* the CM dev-team can do
> > > > about that.
> > > > 
> > > > Currently, there's a way around the issue.  Expect it to
> > > > disappear.
> > > > 
> > > 
> > > Can anyone suggest an alternative reliable free email service?
> > > (That is compatible with Claws, obviously).   I'm about ready to
> > > say "fuck Gmail".    
> > > 
> > > (I only use it as a back-up anyway, in case my main account with
> > > my ISP ever goes bad).
> > > 
> > 
> > App passwords still perfectly work at gmail. Gmail only disabled the
> > ability to auth with account password using "insecure" clients.
> > I really dont understand why everyone is trying to make oauth
> > work....
> > 
> 
> So, how then do I download/upload  my emails from Gmail into
> Claws-mail using POP/SMTP?     (or IMAP).     Oauth was (I think)
> forced on us by Gmail but now they stopped it working (as I
> understand it).
> 
> I keep my emails on my own server hard drive.   Claws lets me do
> that in a way that suits my setup, which is why I use Claws.   I'm not
> interested in the 'cloud'.
> 
> cr

That said, Gmail was refusing to accept Claws authentication last
night, and as of today it's working again.    So I don't know what's
going on.

cr