IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Wed, 09 January 2019 14:35 UTC

Return-Path: <johnl@iecc.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 87049126C7E for <ietf-smtp@ietfa.amsl.com>; Wed, 9 Jan 2019 06:35:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=znjgszSr; dkim=pass (1536-bit key) header.d=taugh.com header.b=tOpmQcDE
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 ptVAzyjXybxW for <ietf-smtp@ietfa.amsl.com>; Wed, 9 Jan 2019 06:35:30 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 7A9511228B7 for <ietf-smtp@ietf.org>; Wed, 9 Jan 2019 06:35:30 -0800 (PST)
Received: (qmail 12719 invoked from network); 9 Jan 2019 14:35:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=31ad.5c3606b1.k1901; bh=gnoMLDVC+2zc3UMWhLXm3kkRdjTXVkIHHUJafjgtBIw=; b=znjgszSrqFIJQf9UKzM/LDkrLR6NbdnoEvJ8AopbDaHmWBvMG9vqTDi2StD3+FfzN4hr0/SAvpG78i9088qSAK0wielZeHf0A5of9U7IChS5OqfI9py/qgvLJM0hBa//fzwFaK06X9Sb/6arj9Xco1HSfyjDXEn4BA60zZd1tWwgyWH5k5TT/m2gubic807akmdalO3qc3sRA9s7Z2QWqeTju50vTF50qDjS3iUDwrDp16U2o0/h6sbkVIOdXBfo
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=31ad.5c3606b1.k1901; bh=gnoMLDVC+2zc3UMWhLXm3kkRdjTXVkIHHUJafjgtBIw=; b=tOpmQcDEJHh9vNodVxaOGGnlSCydddyOFzhgZGXET0gwCcuhGyZaXW+mk6Nq5UONqOfFKcpBN3iS2rI71xDU8iMo2Xx4QNizL7cJ20h72pX25X3evdDXUe8qDAfrFLiRg5R0v+OLc5owisiEm8n6JQPN57yBhvMlVwrFLAhfITA1AKK9f38Bpa6WEwuNswpWcyrMfpfCsfe4R8Ix+TZUv4f6I899ZnfMivFgywKPJ0yPv7GUzOqK+QCl4ODX/DVV
Received: from ary.local ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 09 Jan 2019 14:35:29 -0000
Received: by ary.local (Postfix, from userid 501) id 33122200C76CAD; Wed, 9 Jan 2019 09:35:28 -0500 (EST)
Date: Wed, 09 Jan 2019 09:35:28 -0500
Message-Id: <20190109143529.33122200C76CAD@ary.local>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: giri@dombox.org
In-Reply-To: <CAOEezJTxTN9x_JFXgLidj9k8NVgFTRyqyQc4Aak8UEQuvjiM0w@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/FS-05yRveMVwWWJvEcEpQKT89vA>
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 14:35:32 -0000

In article <CAOEezJTxTN9x_JFXgLidj9k8NVgFTRyqyQc4Aak8UEQuvjiM0w@mail.gmail.com> you write:
>-=-=-=-=-=-
>
>You are right. I was worried that receiving server would not recognize
>"text/markdown" as a media type since it was registered recently in the
>RFC. So if a server started to recognize that as media type, I thought they
>should do that via SMTP extension.

My mail server doesn't support or understand any media types at all.  MIME and
media types are all handled in the MUA.

Please review RFC 5598, the Internet Mail Architecture.  The mail
server that advertises EHLO keywords is an MTA.  MIME types are
handled in the MUA.

Also, practically, every modern MUA handles HTML now.  If you want to use
markdown, adjust your MUA so it translates your markdown into text/html
and sends that.  There are dozens of markdown->html translators so this
is just splicing together code that already exists.

R's,
John

v2.23.0 | Report a Bug | By Email