Re: [Imap-protocol] Gmail LIST-EXTENDED bug
Jamie Nicolson <[email protected]> Mon, 3 Aug 2015 15:37:04 -0700
| Newsgroups | gmane.mail.imap.general |
|---|---|
| Message-ID | <CACU8CfSvckoaP41iaEGB5UygzH6=0de1xV1monxmUS=k4gyAmA@mail.gmail.com> |
--===============7801342834599810814== Content-Type: multipart/alternative; boundary=20cf307d03f4d00f9f051c6fd045 --20cf307d03f4d00f9f051c6fd045 Content-Type: text/plain; charset=UTF-8 This should be fixed now. Thanks for reporting it. On Thu, Jul 23, 2015 at 7:46 PM, Michael M Slusarz <[email protected]> wrote: > Quoting Jamie Nicolson <[email protected]>: > > We can probably fix this in a week or so. Is it causing big problems for >> any clients to have LIST-EXTENDED enabled with this flaw? If it's causing >> serious pain we could turn off LIST-EXTENDED until it's fixed. >> > > Can't speak for anyone else, but this doesn't really affect us. We > fallback to RFC 3501 compliant LIST commands if a LIST-EXTENDED command > fails, so this is simply adding additional round-trips and/or additional > processing on the client side. > > michael > > --20cf307d03f4d00f9f051c6fd045 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">This should be fixed now. Thanks for reporting it.<div cla= ss=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Jul 23, 2015 at 7= :46 PM, Michael M Slusarz <span dir=3D"ltr"><<a href=3D"mailto:slusarz@c= urecanti.org" target=3D"_blank">[email protected]</a>></span> wrote:= <br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef= t:1px #ccc solid;padding-left:1ex"><span class=3D"">Quoting Jamie Nicolson = <<a href=3D"mailto:[email protected]" target=3D"_blank">nicolson@googl= e.com</a>>:<br> <br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> We can probably fix this in a week or so. Is it causing big problems for<br= > any clients to have LIST-EXTENDED enabled with this flaw? If it's causi= ng<br> serious pain we could turn off LIST-EXTENDED until it's fixed.<br> </blockquote> <br></span> Can't speak for anyone else, but this doesn't really affect us.=C2= =A0 We fallback to RFC 3501 compliant LIST commands if a LIST-EXTENDED comm= and fails, so this is simply adding additional round-trips and/or additiona= l processing on the client side.<span class=3D"HOEnZb"><font color=3D"#8888= 88"><br> <br> michael<br> <br> </font></span></blockquote></div><br></div></div> --20cf307d03f4d00f9f051c6fd045-- --===============7801342834599810814== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-protocol mailing list [email protected] http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol --===============7801342834599810814==--