IETF Logo Mail Archive

Re: [Jmap] Draft messages - mutability

Neil Jenkins <neilj@fastmail.com> Fri, 28 April 2017 06:30 UTC

Return-Path: <neilj@fastmail.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 EBE04129457 for <jmap@ietfa.amsl.com>; Thu, 27 Apr 2017 23:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level:
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=eY3h6mP+; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=f+wzW7D+
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 EW5Q2f20Su7A for <jmap@ietfa.amsl.com>; Thu, 27 Apr 2017 23:30:08 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95BF8129441 for <jmap@ietf.org>; Thu, 27 Apr 2017 23:27:38 -0700 (PDT)
Received: from betaweb1.internal (betaweb1.nyi.internal [10.202.2.10]) by mailout.nyi.internal (Postfix) with ESMTP id EBDD720A42; Fri, 28 Apr 2017 02:27:37 -0400 (EDT)
Received: from betaweb1 ([::ffff:10.202.2.10]) by betaweb1.internal (MEProxy); Fri, 28 Apr 2017 02:27:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=BEy+yJJAint+IjoFG3AUz//NDg+nM GP7JudpXCkxKkY=; b=eY3h6mP+Jiq/ZGM3MdOAximgbW6vJAi54/zAn+xxh0W7x DzUwAJSwYkuzQbGrfAkG2sMgP7k5PjJw9gzqh26jXC/McbJA5Of3JhZspmODHg07 PIpOnCru6y3MyjOb/dqMsNtRCMHBldN1IUHvoFGXyeLo7pIxK9n1ku+PS+/mlADM UFRZXDpXciYYcOTc29/3lka8Qp6WnPI0VYrJ8UuRybGUe2MzRsFOg9Jf1XnYLtAB /NjK0+4reNWj8pdWxsJgE73feh2J30ZvpU6YN7oFIFZLGwVtrYj9UMpanIj0Y3nl 8gauFNDzgGcqSQ68cp2+nKdLE+KMOxVTAl9NFc69A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=BEy+yJ JAint+IjoFG3AUz//NDg+nMGP7JudpXCkxKkY=; b=f+wzW7D+FHUsxOzTUNOlcS noqBFNoZoGwghZ4L26YHvnB2/Fiolkuwb41IWJiHYa3h7qkb3M8euvDKSmBOl0/V 1DskvN30ZUmF21p772l7BBkp14f0iCACZKbnAa+z0aosPsGVKPe1aChSJc1ricDg xpdlKnsQybkfZmeSID6Rs89kxjh7yU5Fj3KVYuL9ZfRyrsk2cPqneoi2M6JhwFdK Byn0iedcUT8Uy6oL4pbtmV6eAnBPGZF0chm7Rj6C3Vvje/UscTDZEnYsqi+cdORW uaTmT+vOG41wjM6ag4VQEyHTz/6UFba4YLwN6cWqM81aUDqi5Mg5t8i8sJQ5Qd5Q ==
X-ME-Sender: <xms:2eACWRKxH2L3Lzrs3kWTUxv6G63NcIN18bw3wLu5f2M4Zs23-4Rj8Q>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id BBF47E266D; Fri, 28 Apr 2017 02:27:37 -0400 (EDT)
Message-Id: <1493360857.1167883.959018960.73919234@webmail.messagingengine.com>
From: Neil Jenkins <neilj@fastmail.com>
To: Brandon Long <blong@google.com>
Cc: jmap@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_149336085711678832"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-843b6574
Date: Fri, 28 Apr 2017 06:27:37 +0000
In-Reply-To: <CABa8R6u4WyJoAogwdh0du=BQRmipHiZ37AjRLZadU3NGvBPhGA@mail.gmail.com>
References: <1492998899.3316920.953769616.254C9CBD@webmail.messagingengine.com> <EDDD6045-ECAD-4EAB-AC11-842A9CB2E1CA@oracle.com> <1493084134.2830550.955039432.5403CAFB@webmail.messagingengine.com> <BFB51221-4FD4-4546-B628-595CF76B7F66@oracle.com> <1493087082.2882732.955078288.61343C16@webmail.messagingengine.com> <63973317-543D-4E5C-80D3-16F5979D747D@fugue.com> <1493175371.126749.956396640.2F6911DF@webmail.messagingengine.com> <CABa8R6u4WyJoAogwdh0du=BQRmipHiZ37AjRLZadU3NGvBPhGA@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/HX8S5haYh0osQQ3xI8rtAoltjyk>
Subject: Re: [Jmap] Draft messages - mutability
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, 28 Apr 2017 06:30:10 -0000

On Wed, 26 Apr 2017, at 10:38 PM, Brandon Long wrote:
> In terms of message mutability, we've had another case for plain
> messages that we find complicated, which is if the server chooses to
> modify the message.> 
> As an example case, suppose the server has decided that a message a
> client has already synced is now a phishing message, and as such,
> wants to rewrite all of the links in the message or make them not-
> linkable.
This is an interesting use case, and I don't have a good solution. Do
you have any suggestions for how this replacement might be represented
in JMAP? Happy to consider something, and whether any added complexity
is worth the benefit. I can see this could also be useful in the draft
case being discussed, for other clients to know which draft replaced a
previous one.
Neil.

v2.23.0 | Report a Bug | By Email