Re: [Jmap] Adding the Message::isForwarded property

[Neil Jenkins <[e-mail]>]

On Thu, 27 Apr 2017, at 10:07 PM, Neil Jhaveri wrote:
> Given the discussion above, this makes sense to me, too. My original
> motivation for supporting an isForwarded property was to eliminate the
> incongruence between answered and forwarded. Going back to a keywords
> list achieves that.
OK, I think we have consensus on this. I've made a pull request on
GitHub with the changes[1] for people to review. Two interesting points:
Firstly, I think we should map the 4 \System flags to $System in JMAP.
Using backslash is a real pain because it is an escape character in
JSON, so examples in the spec are confusing if nothing else! Changing it
to $ would make the system keywords consistent with the IANA registered
keywords, which I believe will be less confusing for developers coming
in without an IMAP background. The only issue would be what to do if
someone has added "$Flagged" etc. user keywords on an IMAP server. This
seems unlikely to be much of a real-world occurrence to me, on the basis
it would have been very confusing, but I think we can just specify that
these keywords are not visible over JMAP.
Secondly, matching the setting of the \Answered keyword, I've added a
section that the server SHOULD automatically set the $Forwarded keyword
if appropriate on send (the request that started this whole thread!).
This is looking at the X-Forwarded-Message-Id header though, which as
mentioned earlier in the thread is not a standard (it seems it was first
introduced by Thunderbird).
Any thoughts on either of these, or the change as a whole?

Neil.

Links:

  1. https://github.com/jmapio/jmap/pull/61/files