[sylpheed:37225] Google Mail is at it again, it's now official -- 3rd party apps that do not use OAuth will be disabled
"G.A. L.F." <[email protected]> Fri, 19 Jan 2024 15:00:04 -0800
| Newsgroups | gmane.mail.sylpheed.general |
|---|---|
| Message-ID | <CACWZVi-ZiR4AgXO6NtOB2rYREKkg+kdB2nkj_w96jLv6SfVzJw@mail.gmail.com> |
Greetings Sylpheeders, GMail has announced that (quoting from their email sent out yesterday) "Starting September 30, 2024, Google Workspace accounts will only allow access to apps using OAuth. Password-based access (with the exception of App Passwords) will no longer be supported. POP and IMAP are NOT going away and can still be enabled with apps that connect using OAuth." I have no idea if they only sent this announcement out to paid users that are still using LSA accounts with password authentication, or all of their GMail users (I'm a paid Workspace account user if it matters.) I noticed that last September 2022 Sylpheed released a development version <https://sylpheed.sraoss.jp/en/download.html> of Sylpheed that purports to support OAuth (sylpheed-3.8beta1). I haven't been able to find an RPM for my particular Linux distro, there's only a source code tarball (which apparently includes a spec, so I guess I can just build it myself). My question basically is two parts: - Has anyone tried using the new development release 3.8beta1, and how stable is it? Also, - What is required to switch from password authentication to OAuth? Is it enough to just edit the account(s) configuration and switch the POP3 and SMTP authentication to OAuth, or are any changes required on the Google Workspace admin console side? Cheers, -G