From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] google SMTP with postfix - Password not accepted
Date: Tue, 20 Jun 2023 09:30:49 +0100 [thread overview]
Message-ID: <13290188.uLZWGnKmhe@lenovo> (raw)
In-Reply-To: <d0cbd069-b839-0d67-7ef6-ac8603abc954@sys-concept.com>
[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]
On Tuesday, 20 June 2023 06:29:52 BST thelma@sys-concept.com wrote:
> Trying to send email via Google SMTP and postfix but getting authentication
> failed.
>
> white postfix/smtp[32223]: 62E5618008F: to=<user@google.com>,
> relay=smtp.gmail.com[173.194.203.109]:587, delay=2390,
> delays=2390/0.01/0.29/0, dsn=4.7.8, status=deferred (SASL authentication
> failed; server smtp.gmail.com[173.194.203.109] said: 535-5.7.8 Username and
> Password not accepted. Learn more at?535 5.7.8
> https://support.google.com/mail/?p=BadCredentials
> n3-20020aa78a43000000b00663b712bfbdsm4668932pfa.57 - gsmtp)
>
> relayhost = [smtp.gmail.com]:587
> smtp_sasl_auth_enable = yes
> smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
> smtp_sasl_security_options = noanonymous
> smtp_tls_CAfile = /etc/postfix/cacert.pem
> smtp_use_tls = yes
>
> /etc/postfix/sasl_passwd
> [smtp.gmail.com]:587 USERNAME@gmail.com:PASSWORD
> postmap /etc/postfix/sasl_passwd
> /etc/init.d/postfix restart
>
> The user and password are correct.
I think I know what the problem is - but I do not use postfix and can't
confirm it on my side:
Since mid 2022 Google requires 2FA to allow login into their server. Until
then it used to be the case you could select in their security settings to
"Allow Less Secure Apps", generate an application specific password hash using
their GUI and use this in your mail client. For a year now you won't be able
to do this, unless you first provide a mobile phone number to Google.
If you *must* use Google, they you'll have to login into their Google account
security panel, set 2FA, attempt to connect with your postfix client, create
an application pass code hash for your postfix via their GUI and use that as
your password in your postfix settings. If you change your IP address, or
your PC/client, or anything else Google are using to fingerprint and profile
your device, then you'll have to login again in their GUI to confirm you are
who you are and your client is a legitimate device owned by you.
They have many relevant help pages to explain all this, so you should search
for specific guidance, or find another email provider with less onerous user
profiling demands. ;-)
HTH
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-20 8:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 5:29 [gentoo-user] google SMTP with postfix - Password not accepted thelma
2023-06-20 8:30 ` Michael [this message]
2023-06-20 8:55 ` William Kenworthy
2023-10-14 5:02 ` Peter Humphrey
2023-10-14 7:04 ` Neil Bothwick
2023-10-14 11:26 ` Peter Humphrey
2023-10-14 13:28 ` Peter Humphrey
2023-10-14 21:59 ` Neil Bothwick
2023-10-15 2:43 ` William Kenworthy
2023-10-15 12:33 ` Peter Humphrey
2023-10-15 9:45 ` Michael
2023-10-15 12:31 ` Peter Humphrey
2023-06-20 18:09 ` thelma
2023-06-20 18:26 ` Matt Connell
2023-06-21 5:45 ` thelma
2023-06-20 9:11 ` Dr Rainer Woitok
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=13290188.uLZWGnKmhe@lenovo \
--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