Re: mhlogin stopped working

[Steffen Nurpmeso]

Michael Richardson wrote in
<5853.1595289693@localhost>:
 |
 |> Some hurdles must be taken before being able to use this method.  Using
 |> GMail as an example, an application (that is a name) must be registered,
 |> for which credentials, a “client ID” and a “client secret”, need to be
 |> created and saved locally (in a secure way).  These initial configuration
 |> steps can be performed at
 |
 |But we can't embed a client secret in open source.

Well i did it "for me" (registering the name) only.
It was hard enough to find that developer page and "do it" anyway.

 |Google should know better than this.
 |I'm back to fetchmail with POP3 and the application password.

Google has some trouble, at least for my account.
I still use PLAIN if it is advertised, because i for one do not
like OAuth authentication.  (The Alpine MUA for example included
code to do HTTP queries and JSON interpretation just to be able to
deal with XOAUTH/OAUTHBEARER responses, which are just key/value
pairs.)  And this is what happens since yesterday (once
i encountered it, i do not use that account very often):

  s-nail: >>> SERVER: 220 smtp.gmail.com ESMTP x4sm15187242eju.2 - gsmtp
  s-nail: *smtp-config*: using ehlo extension
  s-nail: >>> EHLO gmail.com
  s-nail: >>> SERVER: 250-smtp.gmail.com at your service, [217.144.132.164]
  s-nail: >>> SERVER: 250-SIZE 35882577
  s-nail: >>> SERVER: 250-8BITMIME
  s-nail: >>> SERVER: 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN 
OAUTHBEARER XOAUTH
  s-nail: SMTP: authentication: skipping PLAIN-CLIENTTOKEN
  s-nail: SMTP: authentication: skipping XOAUTH
  s-nail: >>> SERVER: 250-ENHANCEDSTATUSCODES
  s-nail: >>> SERVER: 250-PIPELINING
  s-nail: >>> SERVER: 250-CHUNKING
  s-nail: >>> SERVER: 250 SMTPUTF8
  s-nail: *smtp-config*: using pipelining extension
  s-nail: *smtp-config*: using auth extension
  s-nail: SMTP: authentication: selecting PLAIN
  s-nail: >>> AUTH PLAIN ....
  s-nail: >>> MAIL FROM:<sdaoden@gmail.com>
  s-nail: >>> RCPT TO:<steffen@sdaoden.eu>
  s-nail: >>> DATA
  s-nail: >>> SERVER: 451 4.5.0 SMTP protocol violation, see RFC 2821 
x4sm15187242eju.2 - gsmtp
  s-nail: SMTP: unexpected status from server: 451 4.5.0 SMTP protocol 
violation, see RFC 2821 x4sm15187242eju.2 - gsmtp

No no.  Or

  s-nail: TLS connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
  s-nail: >>> SERVER: 220 smtp.gmail.com ESMTP q24sm17507947edg.51 - gsmtp
  s-nail: *smtp-config*: using ehlo extension
  s-nail: >>> EHLO gmail.com
  s-nail: >>> SERVER: 250-smtp.gmail.com at your service, [217.144.132.164]
  s-nail: >>> SERVER: 250-SIZE 35882577
  s-nail: >>> SERVER: 250-8BITMIME
  s-nail: >>> SERVER: 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN 
OAUTHBEARER XOAUTH
  s-nail: SMTP: authentication: skipping PLAIN-CLIENTTOKEN
  s-nail: SMTP: authentication: skipping XOAUTH
  s-nail: >>> SERVER: 250-ENHANCEDSTATUSCODES
  s-nail: >>> SERVER: 250-PIPELINING
  s-nail: >>> SERVER: 250-CHUNKING
  s-nail: >>> SERVER: 250 SMTPUTF8
  s-nail: *smtp-config*: using pipelining extension
  s-nail: *smtp-config*: using auth extension
  s-nail: SMTP: authentication: selecting PLAIN
  s-nail: >>> AUTH PLAIN ......
  s-nail: >>> MAIL FROM:<sdaoden@gmail.com>
  s-nail: >>> RCPT TO:<steffen@sdaoden.eu>
  s-nail: >>> DATA
  s-nail: >>> SERVER: 534-5.7.14 
<https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbv
  s-nail: SMTP: unexpected status from server: 534-5.7.14 
<https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbv

Very nice page.  Or, without pipelining:

  s-nail: TLS connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
  s-nail: >>> SERVER: 220 smtp.gmail.com ESMTP q25sm15582101edb.58 - gsmtp
  s-nail: *smtp-config*: using ehlo extension
  s-nail: >>> EHLO gmail.com
  s-nail: >>> SERVER: 250-smtp.gmail.com at your service, [217.144.132.164]
  s-nail: >>> SERVER: 250-SIZE 35882577
  s-nail: >>> SERVER: 250-8BITMIME
  s-nail: >>> SERVER: 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN 
OAUTHBEARER XOAUTH
  s-nail: SMTP: authentication: skipping PLAIN-CLIENTTOKEN
  s-nail: SMTP: authentication: skipping XOAUTH
  s-nail: >>> SERVER: 250-ENHANCEDSTATUSCODES
  s-nail: >>> SERVER: 250-PIPELINING
  s-nail: >>> SERVER: 250-CHUNKING
  s-nail: >>> SERVER: 250 SMTPUTF8
  s-nail: *smtp-config*: using auth extension
  s-nail: SMTP: authentication: selecting PLAIN
  s-nail: >>> AUTH PLAIN .....
  s-nail: >>> SERVER: 534-5.7.14 
<https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbt
  s-nail: SMTP: unexpected status from server: 534-5.7.14 
<https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbt

I guess i now have to bite into XOAUTH permanently.
They should not announce it then, should they.  And they said they
disallow it in 2021, no?  I do not know.

But nice it still works for you at all!

 |]               Never tell me the odds!                 | ipv6 mesh \

Sorry then!

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)