wasm-demo/demo/ermis-f/imap-protocol/cur/1600095039.22707.mbox:2,S

55 lines
2.0 KiB
Plaintext

MBOX-Line: From blong at google.com Tue Oct 16 15:46:35 2012
To: imap-protocol@u.washington.edu
From: Brandon Long <blong@google.com>
Date: Fri Jun 8 12:34:49 2018
Subject: [Imap-protocol] GMail SPECIAL-USE LIST
In-Reply-To: <507D49D5.6070309@flaska.net>
References: <CABHfyPQ8+iqo4Qk+LPU0fZw_ingMBfTC4gRsg2d7aS=LEVqixg@mail.gmail.com>
<C45B6ACD-4C6C-4BEB-A908-D9DBEC0B2FEC@iki.fi>
<9CD3AECA-5993-40DD-B971-8A2DF75B3A94@apple.com>
<CABa8R6sQK2O_p4wb-JMTfCOk9dQxNHut+p0m2DF51G9zG+-Gig@mail.gmail.com>
<507D49D5.6070309@flaska.net>
Message-ID: <CABa8R6tZYMmpjY+w5Y8Cwv2VM3pALYEpTH5f1XAoKkTJYYukew@mail.gmail.com>
On Tue, Oct 16, 2012 at 4:49 AM, Jan Kundr?t <jkt@flaska.net> wrote:
> On 10/15/12 22:45, Brandon Long wrote:
>
>> For those keeping track at home, we had to revert this because a minor
>> phone client wasn't able to handle the extended syntax, hard coding a
>> small set of acceptable list-flags. We'll probably re-enable it as soon
>> as they have a fix.
>>
>
> I assume you are not likely to name the vendor in question. I was
> wondering what the engineering reason for refusing to accept unknown list
> flags might be...
>
Someone made an easy mistake? Unless you pay close attention to the RFC
EBNF, its probably easy to make that mistake.
They haven't shared with me their reasoning. Or their planned fix, though
I did point out that section of the EBNF to them, so hopefully they will
fix it the right way instead of just adding the SPECIAL-USE flags to their
supported list.
Brandon
>
> With kind regards
> Jan
>
> --
> Trojita, a fast e-mail client -- http://trojita.flaska.net/
>
> ______________________________**_________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman2.u.washington.**edu/mailman/listinfo/imap-**protocol<http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20121016/e69da0d1/attachment.html>