Re: [Jmap] Submission

Ted Lemon <mellon@fugue.com> Sun, 23 April 2017 23:49 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 C8E1A1270AC for <jmap@ietfa.amsl.com>; Sun, 23 Apr 2017 16:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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, URIBL_BLOCKED=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 xw9sOSs750Bb for <jmap@ietfa.amsl.com>; Sun, 23 Apr 2017 16:49:18 -0700 (PDT)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (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 DC72D127076 for <jmap@ietf.org>; Sun, 23 Apr 2017 16:49:17 -0700 (PDT)
Received: by mail-qt0-x229.google.com with SMTP id y33so101964875qta.2 for <jmap@ietf.org>; Sun, 23 Apr 2017 16:49:17 -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=P6AOSBqJ8yE7ielPkIQxEccFkPmCfIFN4dbyrjQ11CU=; b=pJtMzNxPoqA6g2yrZyPPo6WBx4Li+6XFQ2Iaut5iPGzZdTcyCJxGTjYZhOtfn86Oft ftDnPWS0YSTgKKSfYY+4AIToqo2JlgCVRAnSCFTsWVFcP3teR6CkSVam4niSujgZuj// 8OtDIdZ6CVwrTUGsTi+7TMmLDtDAiSje/4A4/6kc9bxUSJXxqSOei7uc8Z9PWTNroqjg liCWrnmytLUER0Tgir33Y+uDGcdMat1nE/iY6fw3qTr15z9Elqu09xFQa3cVl1Ya7D9Y hcFH2H8NvWrbXuDyQWPWy4fLuHwO+5xsi8io+ctkcW58atiFtnzEPh/RNWr6pJjrREFO UEAA==
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=P6AOSBqJ8yE7ielPkIQxEccFkPmCfIFN4dbyrjQ11CU=; b=l4iqM3upAGAKy6MyIbfRTQv53jsY1Qp2EAEPlvfkgzL1Ze8unKCWQ7LijJnUkHn2sd FibB272v8gijmFEaRoC81RTab4B5w6wkNHhe5+RZ61CKD32uPwHz6l44+QgkmrnNuLTW u9wPzwQY/XH4Hv5JaSGnSZMNVpfAUekgd/4FrwbADmxreq0G+lJ1zP3SnKwgC/u2INJ2 ZZ0ykpDStRt01ADV62VS6EiW9agwyuGXfmXC5Z1WrveArW1PNZjkemA6/3d5RExpkTFw xwW3XHPvtS8EROe/4y6l3AD0cfKcsQUjcazeb4Kbx0FksnsfgQuXaJX7sflzkvPM1DvL m71w==
X-Gm-Message-State: AN3rC/7SOBFiJ840CQ1MyQAvuYuiQpU7BxqYGgmLJxoxiPwxR+zv5Urx o/EDgpMpJ+ZVMg==
X-Received: by 10.200.42.29 with SMTP id k29mr13228914qtk.186.1492991356892; Sun, 23 Apr 2017 16:49:16 -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 h37sm3213379qtc.47.2017.04.23.16.49.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 23 Apr 2017 16:49:15 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <87F9079E-AAC7-49C7-99FC-79F19AA3C5D6@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_827043B8-DAE1-44D7-BFFF-84C3F66B5DC3"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Sun, 23 Apr 2017 19:49:15 -0400
In-Reply-To: <01QDITVRJT3O00005B@mauve.mrochek.com>
Cc: jmap@ietf.org
To: Ned Freed <ned.freed@mrochek.com>
References: <20170419163429.8556.qmail@ary.lan> <87d1c873cf.fsf@fifthhorseman.net> <alpine.OSX.2.20.1704191353500.43511@ary.qy> <01QDEV2QM6XC00005O@mauve.mrochek.com> <BC098A22-2837-4316-822A-27232A896EF1@fugue.com> <01QDFJV9BBBS00005O@mauve.mrochek.com> <65CA1C64-ACD9-4AF5-8ED4-59D4285B5A8D@fugue.com> <01QDITVRJT3O00005B@mauve.mrochek.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/s8Ev5ZUNNubeYXaDEwZcshxaOcQ>
Subject: Re: [Jmap] Submission
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: Sun, 23 Apr 2017 23:49:20 -0000

On Apr 23, 2017, at 7:13 PM, Ned Freed <ned.freed@mrochek.com> wrote:
> This is a entirely false dichotomy of choices you have going here. Nobody is
> proposing "nailing it to SUBMIT". All anyone is saying is that you need to
> have a means of specifying the envelope separate from the message and its
> headers, and that the envelope needs to be extensible.

If that's the case, then I don't think there's anything to argue about.   But I've been getting the impression that that's not the case.   I am fully in agreement with the assertion, with which I don't recall anyone disagreeing, that the envelope has to be separate from the message and has to be extensible.

My concern is with avoiding a requirement that JMAP submit have the same _flow_ as SMTP submit.   So I want it to be the case that status can be delivered asynchronously, essentially.   I don't mind if it's also possible to deliver it synchronously, since that's just a degenerate case of asynchronous.