IETF Logo Mail Archive

Re: [Jmap] Submission

Jeremy Harris <jgh@wizmail.org> Mon, 24 April 2017 09:44 UTC

Return-Path: <jgh@wizmail.org>
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 C157012EB88 for <jmap@ietfa.amsl.com>; Mon, 24 Apr 2017 02:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham 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 Js-RHm_Kfpk8 for <jmap@ietfa.amsl.com>; Mon, 24 Apr 2017 02:44:20 -0700 (PDT)
Received: from wizmail.org (wizmail.org [IPv6:2a00:1940:107::2:0:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3B7312EB81 for <jmap@ietf.org>; Mon, 24 Apr 2017 02:44:19 -0700 (PDT)
Received: from [2a00:b900:109e:0:c5d6:c61b:f5e0:b51f] (helo=lap.dom.ain) by wizmail.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89_RC100) id 1d2aXX-00086i-Fm for jmap@ietf.org (return-path <jgh@wizmail.org>); Mon, 24 Apr 2017 09:44:15 +0000
To: jmap@ietf.org
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> <87F9079E-AAC7-49C7-99FC-79F19AA3C5D6@fugue.com> <01QDIVTKAWPK00005B@mauve.mrochek.com> <em638a1ecd-f92e-4a6d-b706-5af64fbf0427@bodybag>
From: Jeremy Harris <jgh@wizmail.org>
Message-ID: <20f29006-4ebb-6676-5ac3-31bd559b553f@wizmail.org>
Date: Mon, 24 Apr 2017 10:44:11 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <em638a1ecd-f92e-4a6d-b706-5af64fbf0427@bodybag>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Pcms-Received-Sender: [2a00:b900:109e:0:c5d6:c61b:f5e0:b51f] (helo=lap.dom.ain) with esmtpsa
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/whBZSahG95XMa1jGx4yZ3b49t3E>
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: Mon, 24 Apr 2017 09:44:22 -0000

On 24/04/17 01:54, Adrien de Croy wrote:
> As for other envelope extensions, I agree the SMTP/SUBMIT system needs
> to know certain envelope-related things, such as whether the content is
> binary or 7-bit safe or not.  This is where the discussion about
> shackling JMAP to SUBMIT/SMTP comes in.  It's a shame that we still have
> to support a transport that needs to care about the payload.  Seems like
> a basic layering violation to me.

Specifically on the 8-bit-cleanliness issue:
http://cr.yp.to/smtp/8bitmime.html

-- 
Cheers,
  Jeremy

v2.23.0 | Report a Bug | By Email