Stephen Isard wrote in <[email protected]>: |I'm now getting a slightly different debug output when I do "account |zoho". In particular, I see the credentials that you expected last |time.
No Mr. Isard, you had posted them already. So ok, to reiterate that you now truly have successfully used that python script, as i posted it last, and you can update the access token simply by running it with "--action update"? That would be nice. |s-nail: TLS connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 |s-nail: >>> SERVER: * OK svwall.zoho.com IMAP4 Server (Zoho Mail |IMAP4rev1 Server version 1.0) |s-nail: >>> T3 CAPABILITY |s-nail: >>> SERVER: * CAPABILITY IMAP4rev1 UNSELECT CHILDREN XLIST |NAMESPACE IDLE MOVE ID AUTH=PLAIN SASL-IR XOAUTH2 UIDPLUS ESEARCH |LIST-EXTENDED LIST-STATUS WITHIN LITERAL- ACL CONDSTORE |s-nail: >>> SERVER: T3 OK CAPABILITY completed Sigh, i have not looked into IMAP for over half a decade. But normally a server mentions authentication possibilities via AUTH=X, as shown here for dovecot s-nail: >>> SERVER: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 AUTH=XOAUTH2 AUTH=OAUTHBEARER AUTH=EXTERNAL AUTH=GSSAPI] Dovecot ready. so i am struggling a bit. |s-nail: >>> T4 AUTHENTICATE XOAUTH2 ... |s-nail: >>> SERVER: T4 BAD [CLIENTBUG] syntax: Invalid sasl Argument Well if there really is only AUTH=PLAIN, then it seems to me you would have to switch to the development branch (where it is implemented with credit to yours). v14.9.* does not support it, and honestly i would not understand that provider decision, as written in the other mail. What a plain "XOAUTH2" indicates, i do not know. And what about SMTP, can you now send SMTP via this little MUA over ZOHO? Ciao Stephen, and good night! --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)
