public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Computer system email no not working since gmail change.
Date: Mon, 2 Sep 2024 21:44:29 -0500	[thread overview]
Message-ID: <ab39f7c5-cb3a-3789-7de4-7bbf69b74852@gmail.com> (raw)

Hi,

I posted the other day about my email setup.  Then it hit me, while I
copied the settings over, I never tested it.  So, I tested it.  Sure
enough, no email sent.  Got error messages tho.  I mostly, maybe only,
use this for SMART drive info.  If it detects failure or problems, it
emails me.  Well, it's supposed to anyway.  So, I test by restarting
smartd and it set to send a test email. 

I'm almost certain this started when Google changed the security setup a
few years back.  I've googled and tried the settings others use
including the passkey thingy.  None of it works.  This is the output of
messages for both smartd and smtp.  Check out my fancy egrep.  :-D 


root@Gentoo-1 / # tail -n 50 -f /var/log/messages | egrep 'smartd|sSMTP'
Sep  2 21:23:08 Gentoo-1 smartd[20742]: Monitoring 8 ATA/SATA, 0
SCSI/SAS and 1 NVMe devices
Sep  2 21:23:08 Gentoo-1 smartd[20742]: Executing test of <mail> to root ...
Sep  2 21:25:25 Gentoo-1 sSMTP[20757]: Unable to connect to
"smtp.gmail.com" port 587.
Sep  2 21:25:25 Gentoo-1 sSMTP[20757]: Cannot open smtp.gmail.com:587
Sep  2 21:25:25 Gentoo-1 smartd[20742]: Test of <mail> to root produced
unexpected output (65 bytes) to STDOUT/STDERR:
Sep  2 21:25:25 Gentoo-1 smartd[20742]: mail: cannot send message:
Process exited with a non-zero status
Sep  2 21:25:25 Gentoo-1 smartd[20742]: Test of <mail> to root: failed
(32-bit/8-bit exit status: 256/1)
Sep  2 21:25:25 Gentoo-1 smartd[20742]: Executing test of <mail> to root ...
Sep  2 21:27:40 Gentoo-1 sSMTP[20885]: Unable to connect to
"smtp.gmail.com" port 587.
Sep  2 21:27:40 Gentoo-1 sSMTP[20885]: Cannot open smtp.gmail.com:587



This is a edited version of some config files.  Obvious things like
passwords and such changed. 


root@Gentoo-1 / # cat /etc/ssmtp/revaliases

root:rdalek<annoy the bots>1967@gmail.com:smtp.gmail.com:587
dalerdalek<annoy the bots>1967@gmail.com:587
other_user:rdalek<annoy the bots>1967@gmail.com:587
root@Gentoo-1 / #

root@Gentoo-1 / # grep -v '^#' /etc/ssmtp/ssmtp.conf
root=postmaster
root=rdalek1967@gmail.com  #Change to your preferred email address
mailhub=smtp.gmail.com:587  #Could also use port 587 for STARTTLS Old 465
rewriteDomain=Gentoo-1  #Something to denote your machine's name
FromLineOverride=YES
UseSTARTTLS=YES
#UseTLS=YES
AuthUser=rdalek<annoy the bots>1967@gmail.com
AuthPass=<not real either>  #Special characters seem to barf with ssmtp
#AuthPass=abcdefghijklmnop
mailhub=mail
# hostname=_HOSTNAME_
hostname=Gentoo-1
root@Gentoo-1 / #


I think that is the only config files.  If not, I may have missed one
and that is the problem.  Some things that are commented out are things
I tried with no success.  If someone has a working setup and would like
to share a similar edited version of their files, that would be awesome. 

Any ideas?  Does Google just outright block this now?  If so, I have
another good reason to get rid of gmail.  :-) 

Dale

:-)  :-)


             reply	other threads:[~2024-09-03  2:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03  2:44 Dale [this message]
2024-09-25 20:43 ` [gentoo-user] Computer system email no not working since gmail change 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
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=ab39f7c5-cb3a-3789-7de4-7bbf69b74852@gmail.com \
    --to=rdalek1967@gmail.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