IETF Logo Mail Archive

Re: [ietf-smtp] [Proposal] confusing parts of the mail system, was 250-MARKDOWN

Ned Freed <ned.freed@mrochek.com> Thu, 17 January 2019 13:41 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF935127133 for <ietf-smtp@ietfa.amsl.com>; Thu, 17 Jan 2019 05:41:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.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 78vMJ6x0S5OG for <ietf-smtp@ietfa.amsl.com>; Thu, 17 Jan 2019 05:41:25 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.218.59.24]) (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 980CA1277CC for <ietf-smtp@ietf.org>; Thu, 17 Jan 2019 05:41:24 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01R23VSEGQY800GED8@mauve.mrochek.com> for ietf-smtp@ietf.org; Thu, 17 Jan 2019 05:37:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1547732274; bh=lao35snMAdoiGOab3CehXI54OHSLGC+zIvAmhEW+4Gk=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=Qgh15SWzdyGniuvk3Zw/zwwyGdCedjKx7+sU1Y8dL0QcN+Fy8gpj+9wgufbpAaHP/ 1oWtXV6bwkWu77xDgSVed9FxkIpdPxSbH3dZqrjdutTvSxz8I5xIqvj3eqj6fv8YpZ eL8H4DF4Io2aoVMwqp6fC1ays4SDHQTyDiTg99E8=
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"; Format="flowed"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01R1N39ADWKW00004L@mauve.mrochek.com>; Thu, 17 Jan 2019 05:37:50 -0800 (PST)
Cc: ietf-smtp@ietf.org
Message-id: <01R23VSCZQSG00004L@mauve.mrochek.com>
Date: Thu, 17 Jan 2019 05:36:39 -0800
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Thu, 17 Jan 2019 14:06:28 +0100" <a8016af5-a658-4bef-adb8-164fe80bbee5@gulbrandsen.priv.no>
References: <CAOEezJTxTN9x_JFXgLidj9k8NVgFTRyqyQc4Aak8UEQuvjiM0w@mail.gmail.com> <20190109143529.33122200C76CAD@ary.local> <460d4589-5517-3762-5764-7474523dd09b@digilicious.com> <01R1U95VCAHI00004L@mauve.mrochek.com> <74e22977-8ee8-c762-4882-b56e5911430e@digilicious.com> <CALui8C2qzp_jBo=YHA+XXBGF6+jigDeEaX24L2bohQBdaXKHwg@mail.gmail.com> <2ea48fe6-eb48-02e1-d3e2-53782f3ff758@digilicious.com> <alpine.OSX.2.21.1901111607320.22582@ary.qy> <bcf3958d-cd42-fc3c-57fc-56a5f8394b37@digilicious.com> <alpine.OSX.2.21.1901111647330.22750@ary.qy> <5b6ddc8f-9c53-df04-0f61-721fad0972f3@digilicious.com> <CALui8C3934HTxrY-JGB3rAu1dX1z8oz1AK8jmZLsZQhSuxDszw@mail.gmail.com> <01R238XJND6O00004L@mauve.mrochek.com> <65cc0784-a8f0-e40e-c5d9-c736ee1081ea@digilicious.com> <01R23TPK47AA00004L@mauve.mrochek.com> <64374ebd-6a07-4463-7d3d-a232bd1a475a@digilicious.com> <a8016af5-a658-4bef-adb8-164fe80bbee5@gulbrandsen.priv.no>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/Zef22B8p8JSr-sizHwfefNnzC78>
Subject: Re: [ietf-smtp] [Proposal] confusing parts of the mail system, was 250-MARKDOWN
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2019 13:41:27 -0000

> On Thursday 17 January 2019 13:55:05 CET, Gene Hightower wrote:
> > This something that, I hear, is very difficult for others to do.  I'm
> > told it's very complicated.  Somehow they have figured out how to make
> > this work.

> The difficult bit is what to do if you receive a message that's signed and
> that depends on binarymime, need to forward it, and the next-hop receiver
> doesn't support binarymime. Didn't someone just say that Microsoft gets
> that case wrong?

> The binarymime spec itself isn't very complicated.

Conceptually, maybe, but some of the boundary conditions in a transcoder
are ... interesting.

Add message/global to the mix with nested encodings and it's even more
fun.

				Ned

v2.23.0 | Report a Bug | By Email