Re: [Jmap] Adding the Message::isForwarded property
"Chris Newman" <chris.newman@oracle.com> Mon, 03 April 2017 17:10 UTC
Return-Path: <chris.newman@oracle.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 4F22F120046 for <jmap@ietfa.amsl.com>; Mon, 3 Apr 2017 10:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.998
X-Spam-Level:
X-Spam-Status: No, score=-6.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-2.796, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham 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 orua9eDBOENR for <jmap@ietfa.amsl.com>; Mon, 3 Apr 2017 10:10:46 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE01A128D69 for <jmap@ietf.org>; Mon, 3 Apr 2017 10:10:46 -0700 (PDT)
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v33HAjHc003049 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 3 Apr 2017 17:10:45 GMT
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id v33HAint003641 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 3 Apr 2017 17:10:45 GMT
Received: from abhmp0003.oracle.com (abhmp0003.oracle.com [141.146.116.9]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id v33HAhEe026878; Mon, 3 Apr 2017 17:10:43 GMT
Received: from [10.145.239.159] (/10.145.239.159) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 03 Apr 2017 10:10:43 -0700
From: Chris Newman <chris.newman@oracle.com>
To: Benoit Tellier <btellier@linagora.com>
Cc: jmap@ietf.org
Date: Mon, 03 Apr 2017 10:10:21 -0700
Message-ID: <A9EDBE7D-4E3D-45C2-BB97-F74AC9DB9486@oracle.com>
In-Reply-To: <b5753f7f-92f9-50dd-42f0-ce0de7360e08@linagora.com>
References: <148716911729.17277.15371202023742081890.idtracker@ietfa.amsl.com> <b7ec34d3-3aaf-82af-3663-5b0966c83ff0@dcrocker.net> <b5753f7f-92f9-50dd-42f0-ce0de7360e08@linagora.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.6r5347)
X-Source-IP: userv0021.oracle.com [156.151.31.71]
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/IQIqOSb2j5LEyVrp7goHwse6O80>
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: Mon, 03 Apr 2017 17:10:48 -0000
IMAP $Forwarded is a registered keyword and thus a fully supported part of IMAP: https://www.iana.org/assignments/imap-keywords/imap-keywords.xhtml#imap-keywords-1 There's no need for JMAP to define all these registered keywords; it only needs to reference the registry. = Chris On 3 Apr 2017, at 2:13, Benoit Tellier wrote: > Hello, > > At Linagora, we tend to consider **forward** information as important > for the email we care about. > > Today, it is not part of the RFC-3501 spec, and many IMAP > implementations handle it with the de-facto standard $Forwarded flag. > > This implicit standard is a bad thing, and we truly would like the > JMAP > mail protocol to do this right. To be right, it should be explicit. > > We then propose this pull request: > > It reproduces the behavior of **answered** feature: > > - Adds a **isForwarded** message property > - Adds a mechanism for automatically marking messages as forwarded > upon > sending emails > - Clarifies interactions between isForwarded and threads > - Makes isForwarded searchable > > Does this proposal make sense to you? > > Best regards, > > Benoit Tellier > ----------------------------- > Software engineer at Linagora > PMC on Apache JAMES > > > Le 01/04/2017 à 06:23, Dave Crocker a écrit : >> G'day, >> >> The working group meeting discussion about a static message, dynamic >> annotation, etc., resonated with a variety of similar discussions >> I've >> been around over the years (dating back to the mid-1970.) >> >> A simpler version equates the constructs of message and document, as >> two views of the same thing. (Ie, Document with attributes; Message >> with a body.) >> >> The essence is to consider the nature and relationship of the >> objects, >> possibly permitting different semantics for the same set of objects, >> according to different applications or roles. >> >> That is, there can be a variety of constituent objects that are >> associated and can be viewed according to different semantics (or >> views)... So a message, a document, a calendar entry, a series of >> comments, etc. Each object has associated processing rules (eg, >> static vs. editable vs. executable; constrained choice of values; >> organization into folders or other schemas...) >> >> An environment like this can be powerful and very appealing. The >> challenge tends to be staying practical: With no effort at all it >> devolves into an abstract computer science exercise. Some of that is >> an efficiency issue(*) but I think it's mostly about the human >> manageability for design and operations. >> >> Based on both the years of commercial use and the public commentary >> about the performance, I've no doubt the fastmail system does not >> suffer these downsides. But it's a potential that this re-casting >> through the IETF could easily suffer. >> >> I'm posting this note partly because I think it would exciting to >> produce specs that permit a degree of flexibility that such an >> approach permits, but also wanted to cite the dangers. >> >> At the moment, I'm guessing there needs to be a small number of basic >> object types and a small number of 'relationship' types that define >> the association between objects. These could then be combined into >> higher-order, formal organizations/semantics the define an >> application >> semantic (mail, calendar, whatever.) >> >> >> d/ >> >> (*) A system I did in 1977 has a little bit of this and the extremely >> pure design produced impressively horrible performance. >> > > _______________________________________________ > Jmap mailing list > Jmap@ietf.org > https://www.ietf.org/mailman/listinfo/jmap
- Re: [Jmap] Adding the Message::isForwarded proper… Neil Jhaveri
- Re: [Jmap] Adding the Message::isForwarded proper… Neil Jenkins
- Re: [Jmap] Adding the Message::isForwarded proper… Chris Newman
- Re: [Jmap] Adding the Message::isForwarded proper… HANSEN, TONY L
- Re: [Jmap] Adding the Message::isForwarded proper… Alexey Melnikov
- Re: [Jmap] Adding the Message::isForwarded proper… Neil Jenkins
- Re: [Jmap] Adding the Message::isForwarded proper… Neil Jenkins
- Re: [Jmap] Adding the Message::isForwarded proper… Adrien de Croy
- [Jmap] Spencer Dawkins' No Objection on charter-i… Spencer Dawkins
- Re: [Jmap] Adding the Message::isForwarded proper… Neil Jhaveri
- Re: [Jmap] Adding the Message::isForwarded proper… Neil Jenkins
- [Jmap] message vs. annotation Dave Crocker
- [Jmap] Adding the Message::isForwarded property Benoit Tellier
- Re: [Jmap] Adding the Message::isForwarded proper… Benoit Tellier
- Re: [Jmap] Adding the Message::isForwarded proper… Chris Newman
- Re: [Jmap] Adding the Message::isForwarded proper… Alexey Melnikov
- Re: [Jmap] Adding the Message::isForwarded proper… Benoit Tellier
- Re: [Jmap] Adding the Message::isForwarded proper… Alexey Melnikov
- Re: [Jmap] Adding the Message::isForwarded proper… Benoit Tellier
- Re: [Jmap] Adding the Message::isForwarded proper… Chris Newman
- Re: [Jmap] Adding the Message::isForwarded proper… Neil Jenkins
- Re: [Jmap] message vs. annotation Neil Jenkins
- Re: [Jmap] message vs. annotation Ted Lemon
- Re: [Jmap] Adding the Message::isForwarded proper… Alexey Melnikov
- Re: [Jmap] Adding the Message::isForwarded proper… Adrien de Croy
- Re: [Jmap] Adding the Message::isForwarded proper… Neil Jenkins
- Re: [Jmap] Adding the Message::isForwarded proper… Benoit Tellier
- Re: [Jmap] Adding the Message::isForwarded proper… Chris Newman
- Re: [Jmap] Adding the Message::isForwarded proper… HANSEN, TONY L
- Re: [Jmap] Adding the Message::isForwarded proper… Bron Gondwana
- Re: [Jmap] Adding the Message::isForwarded proper… Neil Jenkins
- Re: [Jmap] Adding the Message::isForwarded proper… Alexey Melnikov