From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 25375 invoked from network); 25 Oct 2022 07:37:10 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 25 Oct 2022 07:37:10 -0000 Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1onEUl-009oYd-H2 for ml@inbox.vuxu.org; Tue, 25 Oct 2022 02:37:07 -0500 Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.96) (envelope-from ) id 1onEUl-002XxX-0Q for ml@inbox.vuxu.org; Tue, 25 Oct 2022 02:37:07 -0500 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.96) (envelope-from ) id 1onEUe-002XxO-19 for ding@lists.math.uh.edu; Tue, 25 Oct 2022 02:37:00 -0500 Received: from quimby.gnus.org ([95.216.78.240]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1onEUZ-008Tnc-2R for ding@lists.math.uh.edu; Tue, 25 Oct 2022 02:36:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:Mime-Version:References:Message-ID:Date:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=OqIAqXbh6Vc2llX91citKJIsF/lZMp+dLUxabo3B39c=; b=QraIOmNQlSszVplxA/aiLPVZz/ w/JBT1t16ZGu8KdWlve9XigwJ/i3MkX4XIi1aPOBUfuuYKFy7OSZXsulKm5B6Sg9+HeoJ/KJkLj+Z Hnwc/UVDa87pjPi+8AfRYP9Mk95sOrhKdT+uuTTFEk3Dr3LtVBdd6ObF6JkTMxfKkUbA=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1onEUN-00089f-QG for ding@gnus.org; Tue, 25 Oct 2022 09:36:48 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1onEUK-0006EW-7I for ding@gnus.org; Tue, 25 Oct 2022 09:36:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Jarmo Hurri Subject: Re: gmail+imap+smtp (oauth2) Date: Tue, 25 Oct 2022 10:36:35 +0300 Message-ID: <875yg8nym4.fsf@iki.fi> References: <87sfpswhy2.fsf@mat.ucm.es> <87r15cjhim.fsf@ucl.ac.uk> <877d7234bl.fsf@undisclosedlocation.com> <87o7u1skek.fsf@iki.fi> <87fsfdb0wf.fsf@undisclosedlocation.com> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) Cancel-Lock: sha1:yvTKd6K6Jjs/cjFkVhCgXUTRTGQ= List-ID: Precedence: bulk Greetings Bob. >>>>> There have been some discussion, either on emacs-devel or here, >>>>> how to make emacs (gnus) work with gmail under those >>>>> circumstances, that is using oauth2. >> >>> I have read accounts of how to make oauth2 work natively with gnus, >>> but I haven't tried it and it seemed "complex and wonderful" >> >> Is there any description anywhere on how this should be set up? > > What I've been doing as an alternative is setting up two-factor > authentication and then generating an app password. This has worked so > far in all instances. > > It's not an ideal solution because two-factor authentication can be a > pain when not using a client. But it's surely the easist to implement. I am using this opportunity to ask a very basic question that might save me a lot of time: does this mean that you need to 2FA every time you initiate an imap connection? > Interesting however, that of my 3 M$ accounts, two require this > process but one still works with the plain old login password. That > one is a corporate account and may have to do with the way the IT guy > set it up. I was told that 1. MS will phase out imap pw connections starting Oct '22 2. this will happen at different times for different customers; for us it happened last week without warning More info here: https://www.microsoft.com/en-us/microsoft-365/blog/2022/09/01/microsoft-retires-basic-authentication-in-exchange-online/ What I do not know yet is what is MS's definition of "Modern Authentication." In particular, does it include app pw and 2FA for imap. All the best, Jarmo