27 lines
1.3 KiB
Plaintext
27 lines
1.3 KiB
Plaintext
MBOX-Line: From barryleiba at computer.org Tue Dec 11 00:57:11 2012
|
|
To: imap-protocol@u.washington.edu
|
|
From: Barry Leiba <barryleiba@computer.org>
|
|
Date: Fri Jun 8 12:34:49 2018
|
|
Subject: [Imap-protocol] RFC 6154 (SPECIAL-USE) and \Important
|
|
In-Reply-To: <78147F1B-B52E-4C3B-A789-C4107E3A6C0C@apple.com>
|
|
References: <ED32D389-FDA8-4FE0-9041-22FEED83071C@apple.com>
|
|
<CABa8R6uiyvqAyHP+Gz89ORYmXigurgPt0xUOUz-gf0d27cXXzQ@mail.gmail.com>
|
|
<78147F1B-B52E-4C3B-A789-C4107E3A6C0C@apple.com>
|
|
Message-ID: <CAC4RtVAe9NhxpdfVfVaPMLHAUOaxUQd1u+Nscxfg4VUN-LKOTw@mail.gmail.com>
|
|
|
|
> I kind of like the idea of amending 6154 to include \Important . 6154
|
|
> already has several Gmail specific mailboxes defined anyway, seems like it
|
|
> might as well add \Important. Plus it would discourage people from adding
|
|
> their own \Important and then clashing with the established meaning that it
|
|
> already has on Gmail.
|
|
|
|
Indeed. I think the thing to do is to write an extension that creates
|
|
a registry for special-use flags, registers the 6154 flags in it, and
|
|
defines and registers \Important. The registry can be defined with a
|
|
policy of "First Come, First Served", and can recommend that
|
|
documentation be provided. Should be short and simple, and I'll be
|
|
happy to help with it if anyone should want to do it.
|
|
|
|
Barry
|
|
|