Aaaaaaaaaaaaaaargh!!!!!!!! I could kill myself!!!!!!!!!!
It's all my fault! I was using an old config file I wrote for protonmail, and since protonmail requires a "bridge" which is closed source, I was using hydroxide... https://github.com/emersion/hydroxide This MIT-licensed software converts your plain ascii protonmail password into the API string that protonmail will require to let you log in; it changes every time you login. I wrote a script which was adding the converted password to the muttrc file at the BOTTOM of the muttrc file, because it was easier to add/delete a line there. So... the password that I was writing at the top of the file, where I define the IMAP properties of my onionmail account was overwritten by that very last line from the old protonmail muttrc file I had used as a template... Now I can login. BTW SMTP requires SASL... thanks, Kevin and Nathan!!! Pau On Sun, Sep 13, 2020 at 10:31 PM Kevin J. McCarthy <[email protected]> wrote: > > On Sun, Sep 13, 2020 at 09:25:18PM +0200, Pau wrote: > >I think this is the issue. That string I was referring to before is > >not the password as defined in my muttrc file. Entering :set > >?imap_pass displays that string, > > To make sure I understand you, :set ?imap_pass is displaying the same > value that appeared in the debug log, not the actual password, correct? > > If that's the case, then mostly likely something else in your > configuration is altering $imap_pass. I would double check whether you > are sourcing another file, or have an account-hook or something else > going on. > > As Nathan noted, the value seems to be base64 encoded binary data. > That might indicate you have done something like: > set imap_pass=`cat foo` > somewhere else in your muttrc and directly read in the base64 data from > some file. > > -- > Kevin J. McCarthy > GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
