MBOX-Line: From nicolson at google.com  Mon Aug  3 15:37:04 2015
To: imap-protocol@u.washington.edu
From: Jamie Nicolson <nicolson@google.com>
Date: Fri Jun  8 12:34:55 2018
Subject: [Imap-protocol] Gmail LIST-EXTENDED bug
In-Reply-To: <20150723204653.Horde.nTSGq462CvKEHJ8L-R7hEVB@bigworm.curecanti.org>
References: <20150723130430.Horde.SA97i23HR6ui9hH7OsaY6OS@bigworm.curecanti.org>
	<CACU8CfTAgfJXZ4VNZqNXZGnFtmiyNh1hwjuYUbQjkjciqxmOew@mail.gmail.com>
	<CACU8CfQvtX7PmGc3-A02qsx6s6Md-=BE-arwEtNZmDNLMEA4pg@mail.gmail.com>
	<20150723204653.Horde.nTSGq462CvKEHJ8L-R7hEVB@bigworm.curecanti.org>
Message-ID: <CACU8CfSvckoaP41iaEGB5UygzH6=0de1xV1monxmUS=k4gyAmA@mail.gmail.com>

This should be fixed now. Thanks for reporting it.

On Thu, Jul 23, 2015 at 7:46 PM, Michael M Slusarz <slusarz@curecanti.org>
wrote:

> Quoting Jamie Nicolson <nicolson@google.com>:
>
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20150803/622e6e7d/attachment.html>
