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

Benoit Tellier <btellier@linagora.com> Fri, 07 April 2017 09:56 UTC

Return-Path: <btellier@linagora.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0B35128BB7 for <jmap@ietfa.amsl.com>; Fri, 7 Apr 2017 02:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yWlaSnDSCwvd for <jmap@ietfa.amsl.com>; Fri, 7 Apr 2017 02:56:53 -0700 (PDT)
Received: from smtp.linagora.com (unknown [109.197.180.137]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 418E812783A for <jmap@ietf.org>; Fri, 7 Apr 2017 02:56:52 -0700 (PDT)
Received: from [10.11.114.151] (unknown [1.55.245.97]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.linagora.com (Postfix) with ESMTPSA id CAFC82673 for <jmap@ietf.org>; Fri, 7 Apr 2017 11:56:49 +0200 (CEST)
To: jmap@ietf.org
References: <148716911729.17277.15371202023742081890.idtracker@ietfa.amsl.com> <b7ec34d3-3aaf-82af-3663-5b0966c83ff0@dcrocker.net> <b5753f7f-92f9-50dd-42f0-ce0de7360e08@linagora.com> <A9EDBE7D-4E3D-45C2-BB97-F74AC9DB9486@oracle.com> <9eb1fd3c-8868-9d24-6c30-46d333b69fef@isode.com> <3c1711a2-46dd-db1c-506e-5e1ad89ce56d@linagora.com> <92769755-62c6-7257-ce3d-7d0b5699735d@isode.com> <59771DE7-35FB-49E3-BFC9-9EBD1268E88A@oracle.com> <1491370605.1381724.934621536.30B3055A@webmail.messagingengine.com> <1d07de41-b115-ccdc-1f12-0eb339c4be0e@isode.com> <1491434028.2437286.935656552.3735299C@webmail.messagingengine.com>
From: Benoit Tellier <btellier@linagora.com>
Message-ID: <ca4acab1-d737-5f93-d436-84ab53cb5a4d@linagora.com>
Date: Fri, 07 Apr 2017 16:56:44 +0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <1491434028.2437286.935656552.3735299C@webmail.messagingengine.com>
Content-Type: multipart/alternative; boundary="------------BF6322B42A365001C16AB711"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/bZRjCbCzJFbSAvONnO5ZJj4a3dE>
Subject: Re: [Jmap] Adding the Message::isForwarded property
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 09:56:56 -0000

Hi Neil,

I took the X-Forwarded-Message-Id from Thunderbird. I did not find more
generic way to convey this information in the headers of the mail.
However I still found this header useful. Hence my proposal.


Otherwise, I definitely agree with having keywords as part of JMAP spec.
I believe we can add mentions about the different keywords defined by
https://www.iana.org/assignments/imap-keywords/imap-keywords.xhtml as
part of JMAP spec.


Would you like me to update my proposal during the following week, to
match the discussion status?


I will include:

 - Keyword field on Messages (Map of keyword to true)

 - GetMessageList logic for keywords

 - The logic about marking messages as $Forwarded when sending them. I
will also include changes about dropping */inReplyToMessageId*./

/  - /The//changes that this implies on Threads (algorithm and order in
display)



Cheers,

Benoit

Le 06/04/2017 à 06:13, Neil Jenkins a écrit :
> On Wed, 5 Apr 2017, at 10:16 AM, Alexey Melnikov wrote:
>
>     Is X-Forwarded-Message-Id registered and which implementations are
>     known to add it?
>
>
> Good question. I took this from Benoit's proposed changes, since we
> would need /some/ header for the server to be able to automatically
> set the $Forwarded flag. Googling suggests this was introduced by
> Thunderbird <https://bugzilla.mozilla.org/show_bug.cgi?id=583587> and
> I don't see any evidence that it is registered anywhere or implemented
> in other clients.
>
> Anyone have further information on this, or know of a more
> standardised alternative? The concept does seem useful to me.
>
> On Wed, 5 Apr 2017, at 03:51 PM, Adrien de Croy wrote:
>
>     Is there no equivalent to set?  E.g. a sorted container whose keys
>     are also the values?
>
>
> No, JSON does not have a built-in "set" representation, hence the
> choice between array or object representation.
>
> Neil.
>
>
> _______________________________________________
> Jmap mailing list
> Jmap@ietf.org
> https://www.ietf.org/mailman/listinfo/jmap