Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
Phillip Hallam-Baker <phill@hallambaker.com> Thu, 09 February 2017 17:05 UTC
Return-Path: <hallam@gmail.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 382D8129C06; Thu, 9 Feb 2017 09:05:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 nEZUpSvEb0fc; Thu, 9 Feb 2017 09:05:35 -0800 (PST)
Received: from mail-yw0-x243.google.com (mail-yw0-x243.google.com [IPv6:2607:f8b0:4002:c05::243]) (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 BAADA129C1A; Thu, 9 Feb 2017 09:05:21 -0800 (PST)
Received: by mail-yw0-x243.google.com with SMTP id l16so735222ywb.2; Thu, 09 Feb 2017 09:05:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=NRN2xol7PfmEIbEWh3SAjpAM0aRz5WBDEBe4N/Y6mHQ=; b=smQBCeEfaT5v+fi+9uugZGBBTU/nVKhEOXZ415CXUNB+cao48/AmQ0GLmWhzjsn/tD KGFJJMJYQhylEfUy6fjXY622dIQitqom55FjR/k+cPgXJRBA8xtvyffS4s+PTfQ6mdFE viYMilcZLlN1Q0qz1/m8tenKRWBUpvBML07vApz4ZwIGt3qVhqWJn8ePGZBZJDam8FuY V9UoF+O4iLC+Aov27IIRiVOTiTGuHW5KAAH6Vt1zglFxxmR2AIlRTXwRtZugm8t2kI2y SLCzcKsQs4MWDKuLweHYRj2C6gIiDCHZq9e+Ev5RykGGyumCLc8DMf9HPW1FDK+f00Nl BFfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=NRN2xol7PfmEIbEWh3SAjpAM0aRz5WBDEBe4N/Y6mHQ=; b=oasFJgO9ctGdLRkAIAX8D/Csb6cpg83A0rHDeNY6/jirxkIRAssG4alzgMBO2pk6x2 +QEeNsVVIywz5ywxi2VzMxFH7L3ts8nN9rLlWeL4bpxkFDTM1T2zA+UlIBlsLPsM/Pql fnwxib+gQep7eYzn5CfmCn8Pv8BABdFf2yD5V7sshzDilT6qZMJvWikh1d/UsS2Jfyvg prgYuz2MyfS34wfBUG0ZJtjUD/KnPVt+yxu0ybAKX1VDWJCXSWosXvQ/8A5xSYfpsH5T uOT/pUZF/0+WFPzI+sEubkiYiy2IWKS8mKjGx2dGhXpS3ee4wsB+ecXdy4OBqfVa7MvM A1eA==
X-Gm-Message-State: AMke39lCPqUpi70ob558XxWMx8f9qesU6GEqxi2iVU6vx8TDaxYEMtk9h4FmI/jPRAZIUCUaM1BEiUCmmMgBbg==
X-Received: by 10.13.213.22 with SMTP id x22mr2966889ywd.165.1486659920857; Thu, 09 Feb 2017 09:05:20 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.17.213 with HTTP; Thu, 9 Feb 2017 09:05:20 -0800 (PST)
In-Reply-To: <03152892-3987-145c-8206-e3ccfe3a7510@isode.com>
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net> <03152892-3987-145c-8206-e3ccfe3a7510@isode.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 09 Feb 2017 12:05:20 -0500
X-Google-Sender-Auth: 5VU0znrrUn4yHuHewMbuKjBW_b8
Message-ID: <CAMm+Lwi=rD27tCJhgYv6RWg1SZ80LuvPRkW6CLQ53UZxxhBjbg@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: multipart/alternative; boundary="001a114fbfca7c10a505481bfc99"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/WPYsIUMCYskMxQoGrUZdvJzQO7Y>
Cc: iesg <iesg@ietf.org>, jmap@ietf.org, Dave CROCKER <dcrocker@bbiw.net>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.17
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, 09 Feb 2017 17:05:36 -0000
One big improvement on the status quo would be to combine the functionality of IMAP and SUBMIT. Having two different protocols doesn't work folk. Particularly since authentication remains a bad joke in SMTP and IMAP. I just sent three copies of the same message to my CEO because my mail app thought it hadn't been sent at all and kept retrying.
- [Jmap] WG Review: JSON Mail Access Protocol (jmap) The IESG
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Randy Bush
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Arnt Gulbrandsen
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Alexey Melnikov
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Alexey Melnikov
- Re: [Jmap] WG Review: JSON Mail Access Protocol (… Phillip Hallam-Baker