From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Making GNUS continue to work with Gmail Date: Mon, 17 Aug 2020 21:47:03 +0000 Message-ID: References: <87imdsgmlw.fsf@mat.ucm.es> <871rkfhkhc.fsf@mat.ucm.es> <875z9p5hnc.fsf@mat.ucm.es> <87364pbkn0.fsf@gnus.org> <87lfihe0zf.fsf@mat.ucm.es> <874kp55l8t.fsf@gnus.org> <87y2mdnwn2.fsf@mat.ucm.es> <87ft8lm5ha.fsf@mat.ucm.es> Reply-To: emacs-devel@gnu.org, Gregory Heytings Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="-212064758-1686466145-1597697224=:16363" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20463"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.21 (NEB 202 2017-01-01) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 17 23:48:01 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k7mz2-0005BV-QK for ged-emacs-devel@m.gmane-mx.org; Mon, 17 Aug 2020 23:48:00 +0200 Original-Received: from localhost ([::1]:45336 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k7mz1-0006nG-Sj for ged-emacs-devel@m.gmane-mx.org; Mon, 17 Aug 2020 17:47:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57804) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k7myJ-0006MS-JG for emacs-devel@gnu.org; Mon, 17 Aug 2020 17:47:15 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:50691) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k7myH-0001TS-BO for emacs-devel@gnu.org; Mon, 17 Aug 2020 17:47:15 -0400 Original-Received: from sdf.org (IDENT:ghe@faeroes.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 07HLl6Ls028059 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Mon, 17 Aug 2020 21:47:07 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 07HLl67c002537; Mon, 17 Aug 2020 21:47:06 GMT In-Reply-To: <87ft8lm5ha.fsf@mat.ucm.es> Content-ID: Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/17 17:47:10 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:253915 Archived-At: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---212064758-1686466145-1597697224=:16363 Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: > > 2. For any other LSA, contact your admin or ask the developer of the app= =20 > you are using to start supporting OAuth. > > 3. *If the developer won=A2t update their app, you will need to switch to= =20 > a client that offers OAuth.* > The issue is not whether Gnus supports OAuth. It does (more precisely, it= =20 is possible to set up a configuration with which it does). OAuth is a=20 standard. The issue is how to use OAuth with Google accounts in a way that is=20 compatible with the GNU principles. For the specific case of G Suite accounts, this issue does not exist,=20 because there is no need for the user, or for those who created the=20 application, to interact with Google: your admin can provide you the=20 necessary OAuth credentials. If you "contact your admin" (see point 2=20 above) and convince them to make your mail client an app that users of=20 your organization can use to access their G Suite mail account, they=20 create a set of OAuth credentials (these are simply two long strings) and= =20 give them to you (and to other users wishing to use the same mail client).= =20 You put these credentials in your mail client configuration, and from then= =20 on it can access your mail account (after going through the OAuth grant=20 process with a browser). Gregory ---212064758-1686466145-1597697224=:16363--