Hello Stephen. Stephen Isard wrote in <[email protected]>: |On Tue, 1 Jun 2021, Steffen Nurpmeso steffen-at-sdaoden.eu |s-nail| wrote: |>|S-nail v14.9.15 under Ubuntu 20.04.2 LTS |> |> Pretty old and buggy. | |Sorry, it's the most recent available in the repository for this |distribution.
Sure. 'Just saying. |> So i just completed my registration for a free account there at |> outlook.office365.com, but whatever i do i cannot get in via this |> little MUA .. even with the current development version. (I was |> short before saying "set imap-auth=oauthbearer", which actually is |> XOAUTH2, but that does not seem to help.) |> Yes, all i get is |> |> s-nail: >>> SERVER: T4 NO AUTHENTICATE failed. |> |> for IMAP | |It's bad enough that I am being forced to use Outlook, I don't really |want to subject you to it as well. If you could just tell me how to |stop that screaming ERROR# from appearing in my prompt, that would be |great. I do not understand your problem really. This string can only be seen if an entry was added to the error log. In a newer version you could "set errors-limit=0" and that should be it. Or compile without errors support at all. |For the record, though, I should have mentioned that I am prompted for a |password after giving the s-nail command. And when I run with -vv, I |see | |s-nail: TLS BLAKE2s256 fingerprint: <long string of hex numbers |separated by colons> |s-nail: TLS connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 |s-nail: P(seudo)R(andom)N(umber)G(enerator): *TLS RAND_* |s-nail: >>> SERVER: * OK The Microsoft Exchange IMAP4 service is ready. |[<long string of letters and numbers>] |s-nail: >>> T1 CAPABILITY |s-nail: >>> SERVER: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 |SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+ |s-nail: >>> SERVER: T1 OK CAPABILITY completed. |s-nail: >>> T2 LOGIN "<account name>" "<password>" |s-nail: >>> SERVER: T2 OK LOGIN completed. |s-nail: >>> T3 SELECT "INBOX" |and so on | |There is also a bunch of stuff about certificates of depths 2,1,0, but |any certificates present came with the Ubuntu distribution and are |nothing that I have done personally for this Outlook account. They use wildcards in the certificate. I now tried for two hours to create an OAuth registration for S-nail, and made it, so that i could use the mutt_oauth2.py script (that is in mutt's contrib/ directory) to get real access tokens, i had to store a file on my web server in .well-known to get that far, whaterver, and i now _do_ have a valid access token NOTICE: Obtained new access token, expires 2021-06-02T17:50:28.440233. but still i cannot use this access token as a password in order to log into my sdaoden at outlook dot com account. I am frustrated and out of ideas. All i know is that our login procedure is correct, it surely is for the development version. Am out really now, very late, want to drive some bicycle. |> That reminds me. Your Alpine just "can"? | |Yes, Alpine connects to it, and if it hits the same error as S-nail, it |doesn't tell me about it. An Android app called K-9 Mail (a Mutt |lookalike) also manages to connect. And, as I said, S-nail connects |too. The initial error report isn't a serious problem, it's just messy. I do not understand the problem. I cannot login. The error marker only happens if there were errors. For v14.10 i will provide a better hook so that access tokens can be updated on the fly via some external script, like mutt_oauth2.py. We do have the *on-main-loop-tick* hook that can be used already, but it is a bit uncomfortable. In general i am totally out of ideas, i had to manually edit the manifest to get myself going at least, what a mess. Ciao, --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)
