send -snoop -nomime -msgid -server smtp.gmail.com -port 587 -tls -sasl -user address@hidden ./foo

[Tom R]

I have a script that runs for example: 

    send -snoop -nomime -msgid -server smtp.gmail.com -port 587 -tls -sasl 
-user examplefoo@gmail.com /a/moobt/tmp/_sendg.msg.AdT

I do not want to use it as a rule, just once or twice a month; otherwise I use 
my own sendmail server.

This send script was working fine for months. Now it fails. I run it on a VPS 
in the cloud. I had to allow plain authetication
in my google account, but that is no longer enough, apparently.

Any tips? Any progress on another type of authetication?

... I may have found a work around from google's msg:

    https://support.google.com/mail/answer/78754 x73sm3543665pfc.98 - gsmtp

Reading all their tips, lead to me clicking on 

    https://accounts.google.com/b/0/DisplayUnlockCaptcha

After I did that. my script started working again.

--
Tom

---

>From ~/.netrc:
machine smtp.gmail.com login REDACTED0@gmail.com password REDACTED1
--

+ send -snoop -nomime -msgid -server smtp.gmail.com -port 587 -tls -sasl -user 
examplefoo@gmail.com /a/moobt/tmp/_sendg.msg.AdT
Trying to connect to "smtp.gmail.com" ...
Connecting to 74.125.204.109:587...
<= 220 smtp.gmail.com ESMTP x73sm3543665pfc.98 - gsmtp
=> EHLO ibisbil.mumble.com
<= 250-smtp.gmail.com at your service, [MYIPADDRHERE]
<= 250-SIZE 35882577
<= 250-8BITMIME
<= 250-STARTTLS
<= 250-ENHANCEDSTATUSCODES
<= 250-PIPELINING
<= 250-CHUNKING
<= 250 SMTPUTF8
=> STARTTLS
<= 220 2.0.0 Ready to start TLS
TLS negotiation successful: TLS_AES_256_GCM_SHA384(256) TLSv1.3
SSL-Session:
    Protocol  : TLSv1.3
    Cipher    : TLS_AES_256_GCM_SHA384
    Session-ID: 
    Session-ID-ctx: 
    Resumption PSK: 
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time: 1628890798
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: no
    Max Early Data: 0
(tls-encrypted) => EHLO ibisbil.mumble.com
(tls-decrypted) <= 250-smtp.gmail.com at your service, [MYIPADDRHERE]
(tls-decrypted) <= 250-SIZE 35882577
(tls-decrypted) <= 250-8BITMIME
(tls-decrypted) <= 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER 
XOAUTH
(tls-decrypted) <= 250-ENHANCEDSTATUSCODES
(tls-decrypted) <= 250-PIPELINING
(tls-decrypted) <= 250-CHUNKING
(tls-decrypted) <= 250 SMTPUTF8
(tls-encrypted) => AUTH PLAIN 
b64<examplefoo@gmail.com[0x00]examplefoo@gmail.com[0x00]3vngjcg1f>
(tls-decrypted) <= 534-5.7.14 
<https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbs
(tls-encrypted) => RSET
(tls-decrypted) <= 534-5.7.14 
ed-WvBxCHIeAUP-K8o6w86ZBP0WUuV6OyHCR8AX3x2McPrFq8hJaZBtFScXXkdb4vsPQB
(tls-decrypted) <= 534-5.7.14 
jeTWC8orhtqGZMXyQDOjnJdxcmzz30m1dEnfolHo45MCk9bZmL9y0WNTH7judF_d>
(tls-decrypted) <= 534-5.7.14 Please log in via your web browser and then try 
again.
(tls-decrypted) <= 534-5.7.14  Learn more at
(tls-decrypted) <= 534 5.7.14  https://support.google.com/mail/answer/78754 
x73sm3543665pfc.98 - gsmtp
(tls-encrypted) => QUIT
(tls-decrypted) <= 250 2.1.5 Flushed x73sm3543665pfc.98 - gsmtp
post: problem initializing server; [BHST] Authentication failed: 5.7.14 
<https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbs
send: message not delivered to anyone