MBOX-Line: From blong at google.com  Mon Dec 10 15:59:06 2012
To: imap-protocol@u.washington.edu
From: Brandon Long <blong@google.com>
Date: Fri Jun  8 12:34:49 2018
Subject: [Imap-protocol] RFC 6154 (SPECIAL-USE) and \Important
In-Reply-To: <ED32D389-FDA8-4FE0-9041-22FEED83071C@apple.com>
References: <ED32D389-FDA8-4FE0-9041-22FEED83071C@apple.com>
Message-ID: <CABa8R6uiyvqAyHP+Gz89ORYmXigurgPt0xUOUz-gf0d27cXXzQ@mail.gmail.com>

Its not documented anywhere that I know of.  That folder is used to
represent the label assigned to messages which are detected as "important"
by our Priority Inbox, and we had folks who use IMAP as an API for Gmail
asking for access to that information.

Its not clear this would ever be a "standard" special-use flag, but I've
also seen a bunch of push back against using the X prefix, so we weren't
clear on which way to go.

We could have just exposed it on XLIST which isn't formally defined, though
that keeps us on special handling for Gmail.

We went with adding it to LIST since special-use (and previous extensions)
already imply that clients need to be flexible in handling these.  We were
worried about that, which is why we created XLIST in the first place... and
when we launched special-use, we did break at least one client which hard
coded a list of acceptable attributes.

Brandon


On Mon, Dec 10, 2012 at 2:54 PM, Ian Anderson <iana@apple.com> wrote:

> I notice that Gmail is including \Important in the result from the LIST
> command.
>
> * LIST (\HasNoChildren \Important) "/" "[Gmail]/Important"
>
> I don?t see that documented in RFC 6154, is that in another RFC?  Or
> documented anywhere?
>
> Ian
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> 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/20121210/3579a760/attachment.html>
