public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Computer system email no not working since gmail change.
Date: Thu, 26 Sep 2024 12:16:12 +0100	[thread overview]
Message-ID: <4624142.cEBGB3zze1@rogueboard> (raw)
In-Reply-To: <61ae6f8b-c889-5c7d-1e4a-2ab493f9bfb6@gmail.com>

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

On Thursday 26 September 2024 11:44:08 BST Dale wrote:
> Michael wrote:
> > On Thursday 26 September 2024 08:28:47 BST Dale wrote:
> >> ssmtp stopped working with a conventional password when Google
> >> introduced 2-
> > 
> > Step-Verification for their GMail account.  Consequently, to be able to
> > continue using ssmtp you need to set up an 'App Password' and use the 16-
> > 
> > character password generated by Google to login:
> >  https://support.google.com/mail/answer/185833
> > 
> > It used to be the case you could set up an 'App Password' without having
> > to
> > provide them with your phone number and other 'none-of-their-business'
> > personal information, but for some years now they have been asking for
> > more
> > information to allow you to complete setting up 'App Password' for your
> > Google account(s) and device(s).
> 
> I also tried the 16 character password method too.  It still didn't work. 

In this case the ssmtp package has outlived its usefulness.  It was always 
limited in what characters it would accept and parse as a password.  It's 
abandonware since 2019 - debian recommends to use msmtp:

https://wiki.debian.org/sSMTP

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-09-26 11:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03  2:44 [gentoo-user] Computer system email no not working since gmail change Dale
2024-09-25 20:43 ` Dale
2024-09-26  7:13   ` covici
2024-09-26  7:28     ` Dale
2024-09-26  8:56       ` Michael
2024-09-26 10:44         ` Dale
2024-09-26 11:16           ` Michael [this message]
2024-09-26 15:42             ` Dale
2024-09-26 17:54               ` [gentoo-user] " Grant Edwards
2024-09-26 17:58                 ` Grant Edwards
2024-09-26 20:20                 ` Dale
2024-09-26 20:42                   ` Grant Edwards
2024-09-26 21:03                     ` Grant Edwards
2024-09-27  0:19                       ` Dale
2024-09-26 21:11                     ` Dale
2024-09-26 21:22                       ` Grant Edwards
2024-09-27  0:08                         ` Dale
2024-09-27  2:40                           ` Grant Edwards
2024-09-27  4:47                             ` Dale
2024-09-27 13:47                               ` Grant Edwards
2024-09-27 14:11                                 ` Dale
2024-09-27 14:48                                   ` Grant Edwards
2024-09-27 15:33                                     ` Dale
2024-09-27 16:00                                       ` Grant Edwards
2024-09-27 16:28                                         ` Dale
2024-09-27 16:53                                           ` Michael
2024-09-27 10:31                       ` Michael
2024-09-27 12:11                         ` Dale
2024-09-27 13:06                           ` Michael
2024-09-27 14:13                             ` Dale
2024-09-26 12:47           ` Grant Edwards
2024-09-26 15:18             ` Dale
2024-09-26 13:42           ` [gentoo-user] " Frank Steinmetzger
2024-09-27 15:51             ` Dale
2024-09-27 16:49             ` John Blinka
2024-09-26 11:49       ` covici
2024-09-26 12:49         ` [gentoo-user] " Grant Edwards
2024-09-26 16:09   ` [gentoo-user] " Matt Connell
2024-09-27 15:58     ` Dale
2024-09-26  9:03 ` Wolfgang Müller

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=4624142.cEBGB3zze1@rogueboard \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.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