Re: [ietf-smtp] [Proposal] confusing parts of the mail system, was 250-MARKDOWN
Ned Freed <ned.freed@mrochek.com> Thu, 10 January 2019 16:17 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 3DB21130E59 for <ietf-smtp@ietfa.amsl.com>; Thu, 10 Jan 2019 08:17: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 nM9dDOjrFN0T for <ietf-smtp@ietfa.amsl.com>; Thu, 10 Jan 2019 08:17: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 50C5F130DC0 for <ietf-smtp@ietf.org>; Thu, 10 Jan 2019 08:17:47 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01R1U95WS5HC00EQKK@mauve.mrochek.com> for ietf-smtp@ietf.org; Thu, 10 Jan 2019 08:12:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1547136762; bh=TsTqPHWMt2r0vRgHaUukKjLRoif/jfb+E5g4oUYhQbM=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=OU7I5Zbz8nBE/BH0A7aXyF2X+UHPDxXgcn2SsAjG2oEE8U1e7NNxperKg6YS2wcHU df9CZjqYtqPREay7DlcR10V5m+mmeAfhPPdRJx6Hx00k2KTOVUMrP2TlP8XskAEGkH GHHYHqdOI+EExk1hdCSr05M3Dl2mTK0psi8cIqmE=
MIME-version: 1.0
Content-transfer-encoding: 8bit
Content-type: TEXT/PLAIN; charset="utf-8"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01R1N39ADWKW00004L@mauve.mrochek.com>; Thu, 10 Jan 2019 08:12:39 -0800 (PST)
Cc: John Levine <johnl@taugh.com>, ietf-smtp@ietf.org, giri@dombox.org
Message-id: <01R1U95VCAHI00004L@mauve.mrochek.com>
Date: Thu, 10 Jan 2019 08:03:09 -0800
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 09 Jan 2019 15:08:43 -0800" <460d4589-5517-3762-5764-7474523dd09b@digilicious.com>
References: <CAOEezJTxTN9x_JFXgLidj9k8NVgFTRyqyQc4Aak8UEQuvjiM0w@mail.gmail.com> <20190109143529.33122200C76CAD@ary.local> <460d4589-5517-3762-5764-7474523dd09b@digilicious.com>
To: Gene Hightower <gene@digilicious.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/MX62SB6JYflHRQwDkvJ3ZfZ9yB8>
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, 10 Jan 2019 16:17:48 -0000
> On 09/01/2019 06.35, John Levine wrote: > > My mail server doesn't support or understand any media types at all. > > MIME and media types are all handled in the MUA. > I agree, except for BINARYMIME: the one MIME type advertised in the > greeting stage of ESMTP. Binary is a content transfer encoding, not a media type. > Does your MTA use a mail store based on mbox files? Many still do; > that means no BINARYMIME. Not true - transcoding is always a possibility, and transcoding requires no understanding of specific media types. This was designed into MIME from the start. > Do you only support DATA for sending mail > bodies (no BDAT); that also means no BINARYMIME. Again, transcoding address this. > Can you imagine the bandwidth saved (and carbon emissions, storage, > etc.) if we had universal support for BINARYMIME? No more encoding > photos and videos as base64 text. Transcoding can also be used to upconvert to binary. These days you have to stay away from transcoding after submission and before final delivery in order not to break signatures, but nothing prevents it from being used on, say, submission. But the availability of the technology doesn't mean people will use it. The asessment of most seems to be that the benefits don't outweigh the costs. > As for text/markdown as a MIME type: it would be nice to have > something lighter than HTML for simple formatted text. But we already > have text/enriched defined in RFC 1896 and that seems to have zero > adoption. > HTML as a “standard” is a dog's dinner. Even if it were true, it doesn't make it any less popular. Ned
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN valdis.kletnieks
- [ietf-smtp] [Proposal] 250-MARKDOWN Viruthagiri Thirumavalavan
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Viruthagiri Thirumavalavan
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Viruthagiri Thirumavalavan
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Gilles Chehade
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Viruthagiri Thirumavalavan
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Gilles Chehade
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN valdis.kletnieks
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Gilles Chehade
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Peter Bowyer
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Viruthagiri Thirumavalavan
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Viruthagiri Thirumavalavan
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Viruthagiri Thirumavalavan
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Viruthagiri Thirumavalavan
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Gilles Chehade
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Viruthagiri Thirumavalavan
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN valdis.kletnieks
- Re: [ietf-smtp] [Proposal] confusing parts of the… John Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… Viruthagiri Thirumavalavan
- Re: [ietf-smtp] [Proposal] confusing parts of the… Brandon Long
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… John C Klensin
- Re: [ietf-smtp] [Proposal] confusing parts of the… Ned Freed
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… John Bucy
- Re: [ietf-smtp] [Proposal] confusing parts of the… John Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… John R Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… John Bucy
- Re: [ietf-smtp] [Proposal] confusing parts of the… valdis.kletnieks
- Re: [ietf-smtp] [Proposal] confusing parts of the… John R Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… John Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… valdis.kletnieks
- Re: [ietf-smtp] message/external-body John R Levine
- [ietf-smtp] Reviving PRDR Дилян Палаузов
- Re: [ietf-smtp] Reviving PRDR John Bucy
- Re: [ietf-smtp] [Proposal] confusing parts of the… John Bucy
- Re: [ietf-smtp] [Proposal] 250-MARKDOWN Keith Moore
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gilles Chehade
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… John R Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… John R Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… John R Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… valdis.kletnieks
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… Ned Freed
- Re: [ietf-smtp] [Proposal] confusing parts of the… John R Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… Ned Freed
- Re: [ietf-smtp] [Proposal] confusing parts of the… John Bucy
- Re: [ietf-smtp] [Proposal] confusing parts of the… John R Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… Jeremy Harris
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] chunking Claus Assmann
- Re: [ietf-smtp] chunking Jeremy Harris
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… Jeremy Harris
- Re: [ietf-smtp] [Proposal] confusing parts of the… John Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… John Levine
- Re: [ietf-smtp] [Proposal] confusing parts of the… Ned Freed
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… Paul Smith
- Re: [ietf-smtp] [Proposal] confusing parts of the… Steve Atkins
- Re: [ietf-smtp] [Proposal] confusing parts of the… Ned Freed
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… Arnt Gulbrandsen
- Re: [ietf-smtp] [Proposal] confusing parts of the… Ned Freed
- Re: [ietf-smtp] [Proposal] confusing parts of the… Ned Freed
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… Arnt Gulbrandsen
- Re: [ietf-smtp] [Proposal] confusing parts of the… Ned Freed
- Re: [ietf-smtp] [Proposal] confusing parts of the… Brandon Long
- Re: [ietf-smtp] [Proposal] confusing parts of the… Gene Hightower
- Re: [ietf-smtp] [Proposal] confusing parts of the… Brandon Long
- Re: [ietf-smtp] Reviving PRDR Phil Pennock
- Re: [ietf-smtp] Reviving PRDR Rolf E. Sonneveld