Thanks for your feedback, Kevin. No, my password does not contain single quotes, but it does contain special characters. I had already thought about this and set a plain ascii passwd with only letters. with the same result. I also have tried with single quotes, without them etc...
I have followed your suggestion regarding my_password, and have run mutt -d 5 and I get these lines: -------------------------------------------- [2020-09-13 20:06:41] 4< * OK WildDuck IMAP Server ready for requests from 178.5.235.201 n4c4sl2k2dfrey45axibpqj [2020-09-13 20:06:41] IMAP queue drained [2020-09-13 20:06:41] 4> a0000 CAPABILITY^M [2020-09-13 20:06:41] 4< * CAPABILITY IMAP4rev1 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN CHILDREN ENABLE ID IDLE NAMESPACE QUOTA SASL-IR UNSELECT XLIST [2020-09-13 20:06:41] Handling CAPABILITY [2020-09-13 20:06:41] 4< a0000 OK CAPABILITY completed [2020-09-13 20:06:41] IMAP queue drained [2020-09-13 20:06:41] imap_authenticate: Using any available method. [2020-09-13 20:06:41] Logging in... [2020-09-13 20:06:41] 4> a0001 LOGIN "xxx" "fFMJITrE20WY9pGYIkg9Mxbbe4EuUqNe9EONwwiSJ7c="^M [2020-09-13 20:06:41] 4< a0001 NO [AUTHENTICATIONFAILED] Invalid credentials [2020-09-13 20:06:41] IMAP queue drained [2020-09-13 20:06:41] Login failed. -------------------------------------------------- LOGIN shows the right username (xxx) but I do not understand what the next string is, "fFMJITrE20WY9pGYIkg9Mxbbe4EuUqNe9EONwwiSJ7c=" This is not my password. Note the escape character as well, as displayed by vim. Does this help you in any way to understand what's going on? As I explained, with k9-mail I do have access to onionmail.org thanks a lot On Sun, Sep 13, 2020 at 6:34 PM Kevin J. McCarthy <[email protected]> wrote: > > On Sun, Sep 13, 2020 at 02:41:12PM +0200, Pau wrote: > >set imap_user=xxx > >set imap_pass=yyy > > Does your password have any special characters? You might want to try > using single quotes: > set imap_pass='yyyy' > > If your password *contains* a single quote, then it should be quoted > like: > set imap_pass='yy'\''yy' > > >et smtp_pass = ${imap_pass} > > There's actually an old bug in Mutt pertaining to assigning directly > from one config variable to another. It will be fixed in the next major > release, but until then I suggest you either duplicate the password or > use a $my_ variable: > set my_pass='yyyy' > set imap_pass=$my_pass > set smtp_pass=$my_pass > > >I recompiled mutt with debugging enabled (Mutt 1.14.7 (2020-08-29) ) > > > >./configure --prefix=/tmp --enable-imap --enable-smtp --enable-debug > >--with-ssl > > > >When running mutt -d 2 I get this: > > Try running at debug level 5. Then you will see the actual > LOGIN username password > as it is sent to the server. That might give a clue what's happening. > > -- > Kevin J. McCarthy > GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
