IETF Logo Mail Archive

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

Ned Freed <ned.freed@mrochek.com> Fri, 18 January 2019 15:36 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 8E88D130E27 for <ietf-smtp@ietfa.amsl.com>; Fri, 18 Jan 2019 07:36:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.208
X-Spam-Level:
X-Spam-Status: No, score=-1.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no 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 swHJGwfSOUPE for <ietf-smtp@ietfa.amsl.com>; Fri, 18 Jan 2019 07:36:47 -0800 (PST)
Received: from mauve.mrochek.com (unknown [66.159.242.17]) (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 6D783130DF1 for <ietf-smtp@ietf.org>; Fri, 18 Jan 2019 07:36:47 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01R25E2UGI3K00GLVX@mauve.mrochek.com> for ietf-smtp@ietf.org; Fri, 18 Jan 2019 07:31:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1547825503; bh=M0Q0kX2VgkhLzUgd/rHGd2JPOxl2tiJ9EIW0hW488lU=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=JsNysuXAyuTrpW0n6DQztnV87Hk5IMR8Lqz9MautWuL7mYH9RMOmb7Ie5OnaWR7X7 lPbvIkRfjSkwItv5jJ9eYqHCvq+G9Bqj73G6CHHfmBOCpTCQOI9Vw3CknMhl84r4yg yfVYr76GgxYQ/N9OTB2mKKUAeIwVC1eOjlmSxtuQ=
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="US-ASCII"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01R1N39ADWKW00004L@mauve.mrochek.com>; Fri, 18 Jan 2019 07:31:39 -0800 (PST)
Cc: Ned Freed <ned.freed@mrochek.com>, John Bucy <jbucy=40google.com@dmarc.ietf.org>, ietf-smtp <ietf-smtp@ietf.org>
Message-id: <01R25E2RXTOG00004L@mauve.mrochek.com>
Date: Fri, 18 Jan 2019 07:28:50 -0800
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Thu, 17 Jan 2019 21:37:57 -0800" <5e6820bc-cb0e-6594-0aec-44c5a71f7a5d@digilicious.com>
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> <01R23VQEHUIQ00004L@mauve.mrochek.com> <5e6820bc-cb0e-6594-0aec-44c5a71f7a5d@digilicious.com>
To: Gene Hightower <gene@digilicious.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/xUIgQl5gIjI2vvzdXtoGsEPW7_4>
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: Fri, 18 Jan 2019 15:36:49 -0000

> On 17/01/2019 05.28, Ned Freed wrote:

> > They have not figured out how to make it work, because it's not
> > possible to make it work in general. Transcoding destroys DKIM
> > signatures, period.

> This mailing list destroys DKIM signatures.

And doing so causes serious problems. Significant effort is underway to address
this in the DMARC WG.

> So: presumably transcoding from 8BITMIME to 7 bit has all the same
> problems, no?

If it were happening now, yes, absolutely.

> But somehow 8BITMIME became common enough for everyone
> to just assume 8 bit transmission now.

Because the transition happened literally decades before DKIM existed.

				Ned

v2.23.0 | Report a Bug | By Email