IETF Logo Mail Archive

Re: [Jmap] Submission

"John R Levine" <johnl@taugh.com> Fri, 21 April 2017 22:54 UTC

Return-Path: <johnl@taugh.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 2BE96129BB7 for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 15:54:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.221
X-Spam-Level:
X-Spam-Status: No, score=-1.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=2jXV+FQ7; dkim=pass (1536-bit key) header.d=taugh.com header.b=XKHNxP2V
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 7eT7cHKhmxNG for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 15:54:42 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31041129AE8 for <jmap@ietf.org>; Fri, 21 Apr 2017 15:54:42 -0700 (PDT)
Received: (qmail 72206 invoked from network); 21 Apr 2017 22:54:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=11a0c.58fa8db0.k1704; bh=tNWWaVwhpIuAroBuJNPwhKZ4QnzZI4BwSezV9MY+E+Y=; b=2jXV+FQ7PFGlfNheF47bexo6xcOQ5ALzCnRlPehVFIR0kYz/d7HI/jG5C7237fp6xNsTrDHVt77BX0l429nJF5HvU+WmWAf6BT35juZIvhMPYxdZbXI9SrNg2PAtuVStPnY3cEBFnYcxTEWaXvZK/42LpvFmkm7JZN0Qr5am5QRCF8ReHQ4+ECRiaobSZNNTy6C2JhAJyMeDyOYMRgWSZgRd5Gtv5z22b0zNYAi1DdJYCDuE/tuqRf3x5vVtY/8n
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=11a0c.58fa8db0.k1704; bh=tNWWaVwhpIuAroBuJNPwhKZ4QnzZI4BwSezV9MY+E+Y=; b=XKHNxP2Vihq5i2oiFxH3Y/VyLfhlybZXaNqn7FRBcAnSHt6Cb9Ghnmm0JTxbz7w6kZeqfCYBpI8bTL2p2vCXKa7NEFG3wwqebj+cG8c8j8gPcopDZxJu6VnnRJorhGw6+hEFA7Ho73j8FJI2dnXaK3Kpzm+1jzh6jzDk0ADloOZiWvjuCG1dJgI6Y4+EF9FRL7ljdo5gEKxw1HJDSaSg8FZJQ2KPZhgMl2JwH2QKraNLsue2UMbjcNwcECo7bSXS
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 21 Apr 2017 22:54:40 -0000
Date: Fri, 21 Apr 2017 18:54:40 -0400
Message-ID: <alpine.OSX.2.20.1704211846410.56587@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Adrien de Croy <adrien@qbik.com>
Cc: "jmap@ietf.org" <jmap@ietf.org>
In-Reply-To: <emc7258396-7955-4388-9259-0425e1b49134@bodybag>
References: <em470cf3b9-5af0-4eb9-a7d0-1d6273df597a@bodybag> <20170421153246.28229.qmail@ary.lan> <emc7258396-7955-4388-9259-0425e1b49134@bodybag>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/2UeKnD3t7RjZX8BrGW2DJx8DVRc>
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: Fri, 21 Apr 2017 22:54:43 -0000

> Also if we don't prevent it, inter-organizational mail could use this as 
> well.  The key is to not make that impossible or worthless.

Hmmn.  I have written submission servers.  They are not particularly 
complicated or difficult, particularly if they don't have to handle the 
crypto goop in STARTTLS and AUTH, both of which JMAP does other ways.

Assuming you mean intra-organizational mail, it would be a big help if you 
could explain concretely what about the standard submission model would 
make such mail impossible or worthless.  Please be specific.

R's,
John

v2.23.0 | Report a Bug | By Email