Re: [ietf-smtp] [Proposal] 250-MARKDOWN

valdis.kletnieks@vt.edu Wed, 09 January 2019 07:34 UTC

Return-Path: <valdis@vt.edu>
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 3C41C12F1A2 for <ietf-smtp@ietfa.amsl.com>; Tue, 8 Jan 2019 23:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 trWOt5Z2lguy for <ietf-smtp@ietfa.amsl.com>; Tue, 8 Jan 2019 23:33:59 -0800 (PST)
Received: from omr1.cc.vt.edu (omr1.cc.ipv6.vt.edu [IPv6:2607:b400:92:8300:0:c6:2117:b0e]) (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 D71D6128766 for <ietf-smtp@ietf.org>; Tue, 8 Jan 2019 23:33:58 -0800 (PST)
Received: from mr4.cc.vt.edu (inbound.smtp.ipv6.vt.edu [IPv6:2607:b400:92:9:0:9d:8fcb:4116]) by omr1.cc.vt.edu (8.14.4/8.14.4) with ESMTP id x097XulP000469 for <ietf-smtp@ietf.org>; Wed, 9 Jan 2019 02:33:57 -0500
Received: from mail-qk1-f200.google.com (mail-qk1-f200.google.com [209.85.222.200]) by mr4.cc.vt.edu (8.14.7/8.14.7) with ESMTP id x097Xp6w008383 for <ietf-smtp@ietf.org>; Wed, 9 Jan 2019 02:33:56 -0500
Received: by mail-qk1-f200.google.com with SMTP id z68so5476861qkb.14 for <ietf-smtp@ietf.org>; Tue, 08 Jan 2019 23:33:56 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:date:message-id; bh=i5NXgMtU24QRGHPqXQSGxTPxA3yV6sK+H2hJ+sUbJ6c=; b=MTl3jOW6gaesCwlGvCKrKheeW3IRlMQVgSSsuo7s7CSTY1nJI/D1K94iKlvXe3KUU9 MKxWkTgV1BJebcYmudDei/c8OYUCZsbynYtwKbGULLdOkUZmOv++XUuB2sBoFYW3M5YT gSDlLN68eVWD7g+VIYIgCjro6zy9LIt3Znr7jxNz/4ks0q6ag08dEDPBt/V+fBMwsUTm uDDfk4NJp6X070K7cxnX0dsv3UdAfxrDLVSo67rQuA3T3EnFkE/qf3J0g0avFv1JlUs1 9TIJtV7UN0kJXop2x75AhbPyOh/AzzBuUJTsYlCVRxSTc9JSmSIfxz310WhUdOmPtnxq m0BA==
X-Gm-Message-State: AJcUukfykDH2InLCx7YECvYrRubPSQj8Bo2SEmlvd6Bew8L1KLQ06yef ZuUP7GI9PJu2326bCWBNhDjaL0eqrdszZ4HO8CgX0Nd6rTeRFMywhNYtojHvc2varyKy5C5yNeQ m9tuu8Hpt1rJAXYmtlGYT2g==
X-Received: by 2002:a0c:f50c:: with SMTP id j12mr4623019qvm.149.1547019231061; Tue, 08 Jan 2019 23:33:51 -0800 (PST)
X-Google-Smtp-Source: ALg8bN7xIQ41v1PzWpZXgGyxK3PEZBV1ic1FkwWcV5th7zb7OHFss5cgPHf9MtzOzxTFZ12pXXp+Aw==
X-Received: by 2002:a0c:f50c:: with SMTP id j12mr4623011qvm.149.1547019230837; Tue, 08 Jan 2019 23:33:50 -0800 (PST)
Received: from turing-police.cc.vt.edu ([2601:5c0:c001:4341::359]) by smtp.gmail.com with ESMTPSA id y6sm16983862qke.34.2019.01.08.23.33.49 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 08 Jan 2019 23:33:50 -0800 (PST)
Sender: Valdis Kletnieks <valdis@vt.edu>
From: valdis.kletnieks@vt.edu
X-Google-Original-From: Valdis.Kletnieks@vt.edu
X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7+dev
To: Viruthagiri Thirumavalavan <giri@dombox.org>
cc: ietf-smtp@ietf.org
In-reply-to: <CAOEezJRwe9iSbGyBfyHNPn8=2avo6bAoFY56++HLY5+FZHhWgw@mail.gmail.com>
References: <CAOEezJRwe9iSbGyBfyHNPn8=2avo6bAoFY56++HLY5+FZHhWgw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 09 Jan 2019 02:33:49 -0500
Message-ID: <4647.1547019229@turing-police.cc.vt.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/cRES5E_X1A-AqY4ALhVPq-IKO7M>
Subject: Re: [ietf-smtp] [Proposal] 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 07:34:00 -0000

On Wed, 09 Jan 2019 12:29:43 +0530, Viruthagiri Thirumavalavan said:

> I wanna bring Markdown support to SMTP.  So instead of transferring both
> "text/plain" and "text/html" versions, future mails can use only
> "text/markdown".

Well, right off the top, there's the end to end problem.

Say you support text/markdown, and your mail server accepts it to deliver. What
happens if my mail server doesn't support markdown?  Do you send a text/markdown
and hope my MUA can deal with it? If you do that, why bother with an SMTP intervention?

Also, see RFC1341, and text/richtext. Ask yourself why you never see e-mails with it.