Re: [Mutt] #3155: tunnel drops, mutt won't quit
#3155: tunnel drops, mutt won't quit
-----------------------+----------------------------------------------------
Reporter: agriffis | Owner: brendan
Type: defect | Status: assigned
Priority: minor | Milestone: 1.6
Component: IMAP | Version: 1.5.19
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Changes (by agriffis):
* status: infoneeded => assigned
Comment:
I'm able to reproduce this with the following sequence:
1. Put in .ssh/config to enable multiplexed ssh connections:
{{{
Host *
ControlPath ~/.ssh/%r@%h:%p-mux
}}}
2. Start a master connection to your server:
{{{
$ ssh -fNM server
}}}
3. Start mutt which should use the master connection for the tunnel.
(Make sure the hostname in your muttrc is exactly the same as what you
used to start the master connection in step 2)
4. In another term, kill the master connection. This can happen, for
example, if the network connection bounces, but we can do it manually
with:
{{{
$ ssh -O exit server
}}}
5. I'm not sure how long you have to wait, but I find that if I use mutt
immediately, it recognizes the connection has gone and behaves
accordingly. If I wait for some period of time, it will still announce
the connection is gone "Tunnel to mail.hp.com returned error 255 ()" but
then it gets into this strange state.
6. I'll attach a debug log. You can see at the end of the log lots of
"Draining IMAP command pipeline". This is what happens when I try to
quit, among other actions.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3155#comment:6>
Mutt <http://www.mutt.org/>
The Mutt mail user agent