mailing list archives

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4383 bytes
Desc: not available
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20121210/8e27ef9b/attachment.p7s>

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?

Sorry for delay, we've updated our docs at
https://developers.google.com/google-apps/gmail/imap_extensions#special-use_extension_of_the_list_command
to mention '\Important' as well, though it's basically repeating what
Brandon has already said.

I'll reach out to Barry to see what we can do about adding this to a
newly-created registry of special-use flags.

>
> Ian
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol

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>

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.

Ian

On Dec 10, 2012, at 3:59 PM, Brandon Long <blong@google.com> wrote:

> 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/f578e435/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4383 bytes
Desc: not available
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20121210/f578e435/attachment.p7s>

> 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