edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: gmail nightmare
Date: Thu, 26 May 2022 14:17:31 -0400	[thread overview]
Message-ID: <20220426141731.eklhad@comcast.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]

I've been using edbrowse to fetch gmail like forever, on pop3 and imap.
I received this email.

---------------
On May 30, you may lose access to apps that are using less secure sign-in technology
To help keep your account secure, Google will no longer support the use of
third-party apps or devices which ask you to sign in to your Google Account
using only your username and password.
Instead, you’ll need to sign in using {Sign in with Google} or other more
secure technologies, like OAuth 2.0. {Learn more}
What do you need to do?
Email software, like Outlook 2016 or earlier,
has less secure access to your Gmail.
Switch to Office 365, Outlook 2019 or newer,
or any other email software where you can sign in using Sign in with Google.
{Learn more}
---------------

WTF.
I obviously can't sign in with google.
Someone kindly wrote what to do in the wiki, like this.

---------------
1. Sign into your Google account.
2. Go to the "security" section.
3. Go to the "app password" section.
4. Generate an app password. Use "Mail" for the app and "Other" for the device (if none of the device descriptions are suitable). Google will generate a password for you to use that is different from your main Google account password.
---------------

That's fine but there is no app password section.
I can't find it anywhere.
Any ideas?
May 30 is coming up fast.

Karl Dahlke

             reply	other threads:[~2022-05-26 18:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 18:17 Karl Dahlke [this message]
2022-05-26 19:18 ` baggett
2022-05-26 19:19 ` Alfonso S. Siciliano
2022-05-27 15:00   ` Serge E. Hallyn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220426141731.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=edbrowse-dev@edbrowse.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).