From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: gmail+imap+smtp (oauth2) Date: Fri, 06 May 2022 10:43:00 +1000 Message-ID: <871qx7scvi.fsf@gmail.com> References: <871qxbdulc.fsf@mat.ucm.es> <87k0b2tkg1.fsf@mat.ucm.es> <87zgjx4qhs.fsf@gmail.com> <87bkwcgmr3.fsf@mat.ucm.es> <87levfzqj2.fsf@yale.edu> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30108"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.7.13; emacs 28.1.50 Cc: emacs-devel@gnu.org To: "Jorge A. Alfaro-Murillo" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 06 02:51:09 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 1nmmBZ-0007d3-CB for ged-emacs-devel@m.gmane-mx.org; Fri, 06 May 2022 02:51:09 +0200 Original-Received: from localhost ([::1]:53200 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nmmBX-0004fm-Vu for ged-emacs-devel@m.gmane-mx.org; Thu, 05 May 2022 20:51:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53428) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmmAy-0003wo-LU for emacs-devel@gnu.org; Thu, 05 May 2022 20:50:32 -0400 Original-Received: from mail-pl1-x636.google.com ([2607:f8b0:4864:20::636]:36589) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nmmAx-0003il-3c for emacs-devel@gnu.org; Thu, 05 May 2022 20:50:32 -0400 Original-Received: by mail-pl1-x636.google.com with SMTP id j14so5944898plx.3 for ; Thu, 05 May 2022 17:50:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:user-agent:from:to:cc:subject:date:in-reply-to :message-id:mime-version; bh=rFzcK+NLg3xLuWbqdq4KnwDtU3iLjl0gG3S0g/QUDhQ=; b=jfz6qhehCMwzww0y7NGBp/9j2RwBYZsKlbcn7biQRGZP7AI8EEoa1o9NOOCGX9alUs N8LPpVuYVMKm+LIOOy+ZjbM40GIWNo2+nh797JvHYaPYmOXOXIIytTlnOKj7XenTItUW giSDB8X62BZJUddLjTPFvIXdAAtGTyHGZm3AihvPQR9pRfE/Ipn56OJOIkyqODy3ClLe cyZpA7A+sskylDJ/L4Zh7x6egKur5Kii4F0vi+KxR8PAHG60t/TUpHtwetyrP1nTGV+/ gv2IuBewJNiqu8lhjZnkw+tvz+hf+MDPe8SPcvl/29RxYNlU5IoZZLdk4n1W6FXVK9Ax 5wdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:references:user-agent:from:to:cc:subject:date :in-reply-to:message-id:mime-version; bh=rFzcK+NLg3xLuWbqdq4KnwDtU3iLjl0gG3S0g/QUDhQ=; b=BsMlLpK6L2J9qWOKKlZSldJRXR3nQe9tJgqp8q3xb4pLLBO/gAx0dskbqWXrDPGfiS MSs9UpinibjIAtPqYi2A5GlWFvJtIg1FBjADBAUUkS2Td6BRqYozCtdnoymPc9oSOuli WbRhaQY4/7guKKN4IiXoOYWF6WykJqlr79L8DaF4i7i2I8BqPEATd8Tlw51J0RxJu7aF 5uxN8x27uDYvo3sqA9gJXKJLBCPwm3SUJW7EMFqvLvdN3vdqquccwEd3aSO42DSqGwiR SiAVTFaoJZLlK75Th5TnpDsiDPuvrCtxjnOcOo4hj1IkSD582Urkn/09LEIky9uanukK kl4w== X-Gm-Message-State: AOAM531DIFWOnOb1XX58Z3ujpS4tci8TfTSYfO1aiPSzJgT5bawzybaT 6w3xDI6lb0siunOuZPdTKtal7CmQYvk= X-Google-Smtp-Source: ABdhPJxQ8EQKxsfWuxNSQX7mZop5EBJUNBo31Hulq13aGfdVINHgGIJeXyr+degJL5Ua9LhllgMdog== X-Received: by 2002:a17:902:cccc:b0:15a:30ec:2f56 with SMTP id z12-20020a170902cccc00b0015a30ec2f56mr1006695ple.169.1651798229322; Thu, 05 May 2022 17:50:29 -0700 (PDT) Original-Received: from dingbat (220-235-29-41.dyn.iinet.net.au. [220.235.29.41]) by smtp.gmail.com with ESMTPSA id z10-20020a655a4a000000b003c5f7623b77sm1962819pgs.74.2022.05.05.17.50.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 05 May 2022 17:50:28 -0700 (PDT) In-reply-to: <87levfzqj2.fsf@yale.edu> Received-SPF: pass client-ip=2607:f8b0:4864:20::636; envelope-from=theophilusx@gmail.com; helo=mail-pl1-x636.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham 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:289291 Archived-At: "Jorge A. Alfaro-Murillo" writes: > On Thu, May 05 2022, Filipp Gunbin wrote: > >> >> Just FTR, with Outlook from Office365 (we had that at work), it is just that - >> you create an app password in web interface (yes, non-free JS), and then just >> put it in authinfo instead of your "account password". > > Just to let you know that (sadly) we have Office365 at my institution but that > they do not allow app passwords. It is something that IT has to allow from the > Office 365 Admin Center. When I called them about it, they told me that they > were only supporting email clients that had 2-factor authentication. > > I haven't been able to use gnus with my work email (@yale.edu) since then. I > wonder if the same is true for other institutions that use Google Workspace. > Yes, this is an issue for institutions that use Google or Office365. The ability to use app passwords is a configuration option for the institution. Both Google and MS will recommend against enabling that option. Far too many IT departmenbts in large institutions will just follow Google/MS advice because they don't understand the issues and because they are not prepared to stick the neck out and go against Google/MS recommendations. > FYI, two free open-source email projects thunderbird (MPL-2.0) and fairmail > (GPL3) work with 2-factor authentication. Is there anyway to use their method of > authentication in gnus? >From what I've read, it is suggested both these projects are not fully compliant with the T&C of Google/MS. This is something some people have attempted to get clarified, but fail to get any response. I think this is precisely the area where the FSF could assist as they might be able to at least get the issue looked at by senior enough Google/MS executives to get a definitive answer. As I understand it, the key issue regards the application ID. Google's T&C imply this must be kept secret (it is an ID assigned by Google once your application has been approved and is used in the code). Problem being, how can you have that ID be in the code and be secret.