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

[Peter Breuer]

But why hasn't the CM project registered at gmail for the OAUTH2 stuff
and then embedded the appropriate certification somehow? Or is it that
each binary build needs a certificate, so it's a distro thing?

I did the OAUTH2 stuff myself, but it's incomprehensible to a human.
*I* registered as a "claws-mail" project and swore various strange
things.  But I never could get beyond getting a TEST certificate because
when I applied for the real McCoy some human came on and asked me some
things I didnt know about.

The TEST setup worked well for a few weeks, but lately it has started to
require renewal every few hours - and certainly if I change location.

It is a huge pain.  I have to use a browser, and be nagged at.

Surely someone only has to do this ONCE, not all users all the time?

To add to the mystery, mailing myself at ieee.org, which is hosted by
gmail,  requires none of this palaver.

By the looks of things, a dedicated authorship team ought to be able to
answer the gmail man where I couldn't and get a full certificate out of
it.  What do they expect one to use?

Regards

PTB