#3641: Latest commit causes mutt to quit after failed password attempt on OSX
10.8.3.
------------------------+---------------------
Reporter: balderdash | Owner: brendan
Type: defect | Status: new
Priority: major | Milestone:
Component: IMAP | Version:
Keywords: |
------------------------+---------------------
Mutt from tip, OSX 10.8.3.
Suddenly, after the April 16 commit, the following occurs (never once
happened before):
I do 'mutt' at the prompt to login to the IMAP server holding my mail
(it's Zimbra).
Next I type the incorrect password (I have $imap_pass unset).
Next mutt says "Zimbra IMAP server terminating connection" (or something
very similar). Then that message disappears and I see "Login failed".
So far, so good. This is as it has always been and how it should be.
But after the Apr 16th commit, this is followed up by *mutt* quitting, and
after it's quit I see output between the last bash prompt and the new one:
"Login failed".
Formerly, mutt wouldn't quit, and the "Login failed" message *inside* mutt
would stay there until I hit another key. I could then do, for example
"c=" to get a fresh password prompt.
This only seems to happen on the account that uses Zimbra. Gmail and my
other accounts (which is either Courier or Dovecot) don't exhibit this.
And I've just verified that there is no problem with commit 4c5163. It's
d3096e that's done this.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3641>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
