IETF Logo Mail Archive

Re: [Jmap] Submission

"John Levine" <johnl@taugh.com> Fri, 21 April 2017 16:01 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 DC84E128B8D for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 09:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level:
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 krns5m6stum3 for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 09:01:11 -0700 (PDT)
Received: from miucha.iecc.com (www.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 E7DEF12878D for <jmap@ietf.org>; Fri, 21 Apr 2017 09:01:10 -0700 (PDT)
Received: (qmail 22847 invoked from network); 21 Apr 2017 16:01:09 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 21 Apr 2017 16:01:09 -0000
Date: Fri, 21 Apr 2017 16:00:47 -0000
Message-ID: <20170421160047.28310.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: jmap@ietf.org
Cc: arnt@gulbrandsen.priv.no
In-Reply-To: <4471fa93-2321-4a7e-87b0-fbb00927d584@gulbrandsen.priv.no>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/W12DQJnpcW3r7ugnj3mmnbvObB8>
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 16:01:12 -0000

In article <4471fa93-2321-4a7e-87b0-fbb00927d584@gulbrandsen.priv.no> you write:
>Assuming that JMAP forwards to the filter or smarthost, then requiring that 
>JMAP servers be able to forward SMTP extensions looks really odd. A 
>submission server on port 587 cannot forward SMTP extensions from its 
>nexthop, why should one on port 443 have to?

Nobody's asking for that.  What we need are the extensions that the
submission server supports.

Perhaps some people here (not you) are unaware that submission and
SMTP are different protocols but share the same set of extensions.

R's,
John

v2.23.0 | Report a Bug | By Email