Re: [Jmap] Draft messages - mutability

Ted Lemon <mellon@fugue.com> Wed, 26 April 2017 02:40 UTC

Return-Path: <mellon@fugue.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 3137C131809 for <jmap@ietfa.amsl.com>; Tue, 25 Apr 2017 19:40:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 JN7_sBlD-XUk for <jmap@ietfa.amsl.com>; Tue, 25 Apr 2017 19:40:08 -0700 (PDT)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 478191273E2 for <jmap@ietf.org>; Tue, 25 Apr 2017 19:40:08 -0700 (PDT)
Received: by mail-qt0-x232.google.com with SMTP id g60so156176324qtd.3 for <jmap@ietf.org>; Tue, 25 Apr 2017 19:40:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ESPPdCVYXcNaWbflrZm9vTgsujNyqzjcQv583k8DXBo=; b=czm99yq0A95myN4gUtevzCdvUmxNAXzvCXRCYTF1tjAlxsJmHWG/X7SJjeLSG9Ff1C EG5yPKmK5QA2NY1NNR6nvqBvL50RkScmNDvkwzAg0QTMTmCVFdDAGstx/6FncMMIclMd t/4POaYXtZH5qdHMH01oK4XG0WC2R+DrB5Fzng2VPTtg4jl7XBPgvpDh7gLnArJ3V0UI 4+paLyBxgxrrjFe/VlLZrbjIDQiBMykmY7MYMAy9SbNixI06oEWQ81eO1mf0LbzMlSVm iCwpjmqjX+ztFSE5yJbWgwyJKMKvzxhNXBifU1Jh31CTuFzNIblyMeMk0WdvZegnMqhO n3Hg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ESPPdCVYXcNaWbflrZm9vTgsujNyqzjcQv583k8DXBo=; b=MsztMQBir5JCaJoNoXiaQdbtUYUcm/0UiGSmDCwXY47aeRXTZ2h1hP9V+ZQGihKuoh lgXI7EzbV341zkmowImkPwnqVWZnudHSEyxq3gkah9lip9DtDA5BP87/LXAl1gNrkvat +bdvxg/nTkDR4EiZuPSnwNefGPlbdCmLN4eZ+Q/qFl/4lpQAkoGVkAqUpIAlGc4eDdLb Hb2wOaTNqnY9DLbCzj7iywajGjRvgFuN6xFEjx5WTGlRaDDvA5pO/eoDjANB8u3FQkgF QTPV9Dq9g2MKFChA1DtUpx+NXqLo0SuI07lluR9baOOhuCpX/A8Dxwugo58TXe8TgXxS INSg==
X-Gm-Message-State: AN3rC/6AH6+sp9B8aSE7q2Ua24l3jYC9yOzHFYQW6v+CV0xvWwK4R5CH JIGdlyeU4Dlp3ZxTMlA=
X-Received: by 10.237.62.115 with SMTP id m48mr34695505qtf.192.1493174407434; Tue, 25 Apr 2017 19:40:07 -0700 (PDT)
Received: from macbook-pro-6.home (pool-108-31-94-75.washdc.fios.verizon.net. [108.31.94.75]) by smtp.gmail.com with ESMTPSA id n5sm16503763qtd.7.2017.04.25.19.40.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Apr 2017 19:40:06 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <63973317-543D-4E5C-80D3-16F5979D747D@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D43457ED-D90A-4F2D-886D-CAC9B17F9EDB"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 25 Apr 2017 22:40:05 -0400
In-Reply-To: <1493087082.2882732.955078288.61343C16@webmail.messagingengine.com>
Cc: Chris Newman <chris.newman@oracle.com>, jmap@ietf.org
To: Neil Jenkins <neilj@fastmail.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>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/ILzCFk00Fs2Zog3ben8036ZV3j4>
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: Wed, 26 Apr 2017 02:40:10 -0000

On Apr 24, 2017, at 10:24 PM, Neil Jenkins <neilj@fastmail.com> wrote:
> Now with immutable messages, all my laptop MUA can see is that the draft has been deleted from the server, but this might just mean there's a newer version of the draft. I can see the newer draft but can't know for sure it's an update to the one I have open or not. So I can either resave the draft that's open (which could cause a duplicate old draft to "reappear" in the Drafts mailbox), or I can just delete it and hope for the best (and the user can reopen the new draft if they still hadn't finished sending).

I can see where this can happen if the client hasn't synchronized with the server, or if the message has been modified on the client before the sync happened, but in the normal case where the client is up to date, shouldn't the old version of the draft be gone from the list of drafts, and the new one present?   It's not like the _user_ is going to look at the message ID.

I suppose that if the old draft were present in a viewer, the user would see the weird behavior of the viewer disappearing, and they'd have to go click on the message again, so it would be good to have a way to discover the message that replaced it and open that one when removing the old one from the viewer.   And of course the MUA would have to notice that the old draft is no longer marked as in the draft folder, and possibly is marked as in the trash folder, and know to take some action because of that.