From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-199106-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 70DDB158094
	for <garchives@archives.gentoo.org>; Thu, 30 Jun 2022 14:29:20 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id C5825E0A04;
	Thu, 30 Jun 2022 14:29:13 +0000 (UTC)
Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 09F22E09F3
	for <gentoo-user@lists.gentoo.org>; Thu, 30 Jun 2022 14:29:11 +0000 (UTC)
Received: from list by ciao.gmane.io with local (Exim 4.92)
	(envelope-from <lnx-gentoo-user@m.gmane-mx.org>)
	id 1o6vAL-00069l-QD
	for gentoo-user@lists.gentoo.org; Thu, 30 Jun 2022 16:29:09 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: gentoo-user@lists.gentoo.org
From: Grant Edwards <grant.b.edwards@gmail.com>
Subject: [gentoo-user] Re: Google pop3 authentication failure
Date: Thu, 30 Jun 2022 14:29:03 -0000 (UTC)
Message-ID: <t9kbvf$miu$1@ciao.gmane.io>
References: <Yqc+z9PXdSuaX4GB@waltdnes.org> <YqdN9E9kXXNs9aaz@desktop>
 <YrzIal3sdItgbjej@waltdnes.org> <t9ijjf$cdm$1@ciao.gmane.io>
 <Yrz8oXXG+GUA4SNz@waltdnes.org>
User-Agent: slrn/1.0.3 (Linux)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
X-Archives-Salt: e49bec8b-3495-486c-93e4-69fb992232b4
X-Archives-Hash: 1b77a123be220406c568080ce890afe0

On 2022-06-30, Walter Dnes <waltdnes@waltdnes.org> wrote:
> On Wed, Jun 29, 2022 at 10:26:55PM -0000, Grant Edwards wrote
>> 
>> AFAIK, you've got two choices.
>> 
>>  1. Use an "app password"
>>  
>>     https://support.google.com/accounts/answer/185833
>>     https://www.lifewire.com/get-a-password-to-access-gmail-by-pop-imap-2-1171882
>> 
>>  2. Use OAUTH 2.0
>>  
>>     https://developers.google.com/gmail/imap/xoauth2-protocol
>>     https://oauth.net/2/
>
> I looked at those instructions and also at setting up mutt, which I
> currently use.  Clear as mud.

OAUTH is pretty complicated.

However, setting up an app password is very simple. It only takes a
few clicks. Quoting from the google support page (first link above):

1. Log in to your Google Account.
2. Click "Security".
3. Click "App Passwords".

That brings up the App Paswords page

4. Select app (pick app from dropdown, you want "Mail")
5. Select device (pick device from dropdown, pick whatever you want, I recommend custom)
6. Click "Generate"

That will pop up a dialog containing a 16-character password to be used by fetchmail. Copy that password

7. Click "Done"