On Thursday, 21 April 2016 at 10:06, Kevin J. McCarthy wrote: > On Thu, Apr 21, 2016 at 05:19:00PM +0100, Arnt Gulbrandsen wrote: > > > One workaround is to send the three commands separately, not at the same > > time. I don't like that, it slows down login in all cases and if really is > > pipelining, then I don't feel confident that the bug only affects THIS > > instance of pipelining. Mutt will pipeline in other cases too. > > I suppose we could try that, but I agree this is less than ideal, and > Mutt does using the pipelining in other places. Is Mutt doing > something wrong here (posed to you too Brendan)?
I don't believe mutt's pipelining is in the wrong here, no. RFC 5161 explicitly says: There are no limitations on pipelining ENABLE. For example, it is possible to send ENABLE and then immediately SELECT, or a LOGIN immediately followed by ENABLE. > > Another is to gate ENABLE on UTF8=ACCEPT. Which is less slow but uhm. > > Actually the reporter said that particular "fix" didn't work. The only > thing that worked was setting $imap_pipeline_depth to 0 or 1. > > I'm inclined to leave it at that, unless Mutt is doing something wrong. >
