IETF Logo Mail Archive

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

John C Klensin <john-ietf@jck.com> Wed, 09 January 2019 23:27 UTC

Return-Path: <john-ietf@jck.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 B55E812D84D for <ietf-smtp@ietfa.amsl.com>; Wed, 9 Jan 2019 15:27:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 VyQysI4piPkY for <ietf-smtp@ietfa.amsl.com>; Wed, 9 Jan 2019 15:27:08 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22CAF129508 for <ietf-smtp@ietf.org>; Wed, 9 Jan 2019 15:27:08 -0800 (PST)
Received: from localhost ([::1] helo=JcK-T100) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ghNFU-000JWk-TG; Wed, 09 Jan 2019 18:27:01 -0500
Date: Wed, 09 Jan 2019 18:26:58 -0500
From: John C Klensin <john-ietf@jck.com>
To: Gene Hightower <gene@digilicious.com>, John Levine <johnl@taugh.com>, ietf-smtp@ietf.org
cc: giri@dombox.org
Message-ID: <71891355DC29DF499EAD2037@[192.168.1.100]>
In-Reply-To: <460d4589-5517-3762-5764-7474523dd09b@digilicious.com>
References: <CAOEezJTxTN9x_JFXgLidj9k8NVgFTRyqyQc4Aak8UEQuvjiM0w@mail.gmail.com> <20190109143529.33122200C76CAD@ary.local> <460d4589-5517-3762-5764-7474523dd09b@digilicious.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/mzmAWvsytpJJcRnJGIWlrf2D8ds>
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: Wed, 09 Jan 2019 23:27:10 -0000


--On Wednesday, January 9, 2019 15:08 -0800 Gene Hightower
<gene@digilicious.com> 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.

Even that is dubious.  What BINARYMIME does an SMTP extension is
to enable the use of those media types; it does not require or
specify them.

>...
> 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.

Actually, fairly heavily adopted in the early days, just largely
irrelevant, as a little markup but not much, since text/html was
specified and took over

v2.23.0 | Report a Bug | By Email