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

29 lines
1.1 KiB
Plaintext

MBOX-Line: From jkt at flaska.net Tue Oct 16 04:49:41 2012
To: imap-protocol@u.washington.edu
From: =?UTF-8?B?SmFuIEt1bmRyw6F0?= <jkt@flaska.net>
Date: Fri Jun 8 12:34:49 2018
Subject: [Imap-protocol] GMail SPECIAL-USE LIST
In-Reply-To: <CABa8R6sQK2O_p4wb-JMTfCOk9dQxNHut+p0m2DF51G9zG+-Gig@mail.gmail.com>
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>
Message-ID: <507D49D5.6070309@flaska.net>
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...
With kind regards
Jan
--
Trojita, a fast e-mail client -- http://trojita.flaska.net/