Date: Sun, 18 Jul 2021 20:20:05 +0200 From: Ralf Mardorf <ralf-mardorf@riseup.net> To: freebsd-questions@freebsd.org Subject: Re: Claws Mail (was: What the hell starts pulseaudio?!) Message-ID: <351c2b55514490582d42e6434d90fefebaaf3eb2.camel@riseup.net> In-Reply-To: <14b675f9-a4fd-608f-719c-b26274fcc2b6@gmail.com> References: <20210718134409.5e8d545a@archlinux> <14b675f9-a4fd-608f-719c-b26274fcc2b6@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2021-07-18 at 17:07 +0000, Roderick wrote: > On Sun, 18 Jul 2021, Ralf Mardorf wrote: Note, I forwarded this quote from Paul, a Claws developer... > > I'm not understanding what this "CLIENT ID" is that you are talking > > about, if it is not OAuth2. But OAuth2 is not automatic in claws-mail, > > and it is not (currently?) necessary for connecting to gmail servers. > > There is some pressure from google. One must continuously enable > "less secure apps", otherwise OAuth2 is the only alternative. ...and the Claws developer knows all this, but there's a lot of confusion by users. The reason that I described how it works for Yahoo is, to explain users (not the developer), that the passwords by the well known Claws settings get replaced by passwords, that were generated by the Yahoo Webinterface. Nothing does change when using Claws, just the password is generated by Yahoo. There is nothing "two" things whatsoever. It's all the same password usage as before, just that Yahoo generates the password for each external mail client accessing a Yahoo account, as described by https://uk.help.yahoo.com/kb/new-mail-for-desktop/learn-generate-third-party-passwords-sln15241.html . Old passwords don't work anymore, there was the need to replace the old passwords, by those new generated passwords. For Google it's probably the same.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?351c2b55514490582d42e6434d90fefebaaf3eb2.camel>