From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: gmail+imap+smtp (oauth2) Date: Wed, 04 May 2022 17:35:45 +0200 Message-ID: <87zgjx9upa.fsf@telefonica.net> References: <871qxbdulc.fsf@mat.ucm.es> <877d72nf3h.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12110"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:AsWoWU94tQKprXxPMnLVVfujW7M= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 04 17:36:38 2022 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 1nmH3O-0002yh-FU for ged-emacs-devel@m.gmane-mx.org; Wed, 04 May 2022 17:36:38 +0200 Original-Received: from localhost ([::1]:54266 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nmH3N-0006fO-1B for ged-emacs-devel@m.gmane-mx.org; Wed, 04 May 2022 11:36:37 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34890) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmH2g-0005KM-HI for emacs-devel@gnu.org; Wed, 04 May 2022 11:35:54 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:43256) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmH2e-0007OY-IU for emacs-devel@gnu.org; Wed, 04 May 2022 11:35:54 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nmH2c-0001jS-3f for emacs-devel@gnu.org; Wed, 04 May 2022 17:35:50 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:289186 Archived-At: Tim Cross writes: > Google introduced the concept of app passwords back when they first > implemented 2FA. Basically, they are just a password based > authentication workflow which can be used with applications that do not > support 2FA or oauth2 based authentication and authorisation. [snip] > Google is removing access to imap/smtp using your main google > login/password and will require 2FA and oauth2 for all web based > authn/authz. However, their documentation implies that app passwords > will remain as the standad solution for applications which cannot do 2FA > or oauth2. If I read this right: https://support.google.com/accounts/answer/185833?hl=en app passwords require to have 2FA turned on. So you have to go through the 2FA process anyway with app passwords.