IETF Logo Mail Archive

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

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 15 June 2017 10:36 UTC

Return-Path: <alexey.melnikov@isode.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 83C6E126C25 for <jmap@ietfa.amsl.com>; Thu, 15 Jun 2017 03:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
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 Pnn5GM5M8kuT for <jmap@ietfa.amsl.com>; Thu, 15 Jun 2017 03:36:13 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 09672120046 for <jmap@ietf.org>; Thu, 15 Jun 2017 03:36:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1497522972; d=isode.com; s=june2016; i=@isode.com; bh=L76XZnt16B7672ynHrcfJ2NEwtvPrfNs7aob4syWO7Q=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=RQ1EhHvzp9mMGSWb5lvq/ewGsfqtmkTRf9vHSYquFQEji6Kg850mkHfegCoV2k9q3AlPnq B0IJda3RbIoUaJuDo4m859AuzYHJ3yF5AwAAQi45F+BrQt45ajSEkdoXH2/LFMlv0DVUSr e/G0aFFwhMChlocgVSh9Hb4rkBYOmvk=;
Received: from [10.215.149.46] ((unknown) [85.255.237.187]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <WUJjGwBwY536@statler.isode.com>; Thu, 15 Jun 2017 11:36:12 +0100
X-SMTP-Protocol-Errors: NORDNS PIPELINING
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPhone Mail (13G35)
In-Reply-To: <1497493289.1841083.1009922936.5BAEB289@webmail.messagingengine.com>
Date: Thu, 15 Jun 2017 11:54:51 +0100
Cc: jmap@ietf.org
Message-Id: <FA8AA3AA-E988-4019-B29D-2D630FAF42D5@isode.com>
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> <27c62cc8-68e0-49b5-4900-34c26d7b4c6a@linagora.com> <C88A669A-2143-4FC2-81EF-3C9A2CD5963B@apple.com> <D0072AC9-71DC-4831-A3DA-FEA4A7B85BBA@oracle.com> <AB5279CE-4F9A-4DE8-AEEA-E1425D04FA89@att.com> <1492581452.3025596.948906456.71780673@webmail.messagingengine.com> <1A7624AF-2FD9-4FE8-A29D-23BFADEED04B@apple.com> <1493360522.1171603.959013464.217C003E@webmail.messagingengine.com> <1497493289.1841083.1009922936.5BAEB289@webmail.messagingengine.com>
To: Neil Jenkins <neilj@fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="Apple-Mail-7A2225A7-906C-405C-A5E9-2DF0BFB43C2B"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/LMQM3I_BnA60_g-1fTYB4naVeNs>
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: Thu, 15 Jun 2017 10:36:14 -0000

On 15 Jun 2017, at 03:21, Neil Jenkins <neilj@fastmail.com> wrote:

>> 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).
> 
> The current draft references `X-Forwarded-Message-Id`, but should a Forwarded-Message-Id header perhaps be standardised?

Yes.

v2.23.0 | Report a Bug | By Email