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

Viruthagiri Thirumavalavan <giri@dombox.org> Wed, 09 January 2019 07:40 UTC

Return-Path: <giri@dombox.org>
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 CF803128CF3 for <ietf-smtp@ietfa.amsl.com>; Tue, 8 Jan 2019 23:40:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dombox.org
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 7zKfCv_2QlBZ for <ietf-smtp@ietfa.amsl.com>; Tue, 8 Jan 2019 23:40:46 -0800 (PST)
Received: from mail-yw1-xc32.google.com (mail-yw1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 318AA128766 for <ietf-smtp@ietf.org>; Tue, 8 Jan 2019 23:40:46 -0800 (PST)
Received: by mail-yw1-xc32.google.com with SMTP id k188so2607541ywa.6 for <ietf-smtp@ietf.org>; Tue, 08 Jan 2019 23:40:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dombox.org; s=default; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Gyykz54q28PvCgMujYmuJ+Ct4LtWEy6MaFFsf/faO4I=; b=g+5dxkoQH1LM9DXVAa+hoQBaH+FxXP8yn9q66mIv9xfjE/b7vnIN7onWhySyFXCu0R jTd2Z6UrVr++hP0hGelcNqh23ZTFIXrtZB0hGXeMwKzXate7p4z/nn/de7yHIGXjZJeT wITqkoN42jHNpuEGeNXcES0ps2cXRD4ZER9G6tPHVaYBcfsX1cgtBCUmZZ1FNHBMIIEx RFWk5pZhtjnx4u/JclTDXoqrX6AOxpPVtXgVUyykJI4CB3+wh+bjYZ2geqb/Kug9nKIV osOUDU8BNWtekSYPDPpaGVXOivd7iwc6KJ9Hh4+hLvTgHsjxjaMFUdrOLk+Zy/iZhfPH ZTmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Gyykz54q28PvCgMujYmuJ+Ct4LtWEy6MaFFsf/faO4I=; b=eoESkrZIK2d7UP0OjwQx9CNrj+kq37dbmrJpRS7Yu0jb123Q1/GeCNDd4oJDeXxirR 0hGZLU7x7KN/CmlxZw9cI2OKtBHD1eST37Aai59oHIC5D6EB5KfDRnCVInDwxDoQGf11 CTIW84WNvvusnXVWN/HHnQmFu2mphSj3HmnM2Xu2cu8ZocLMAevssxUDKoe/Eqj21w8x ODjm66vp3zUI4y7HFbgGtplCJx1Rq21BuaXsqNZG3RFQAwnCKMOt81lb04TwnpHYgs4K iVCIzv3LHgNTcIB9zRF/3mK2yBJckEvXAxJ/2r+8Tjv8enXXJLOehD3RSiqTuTsG9y7/ dIRQ==
X-Gm-Message-State: AJcUukdNEQLIG0VSva6hOaBSeQbBMxKaNpFW3KHjNqIKcXmIYnYTjNAV TEncMsnyJFP42tL1nsaxKDSGm98DQztzvV+4h4+pf4JqolU=
X-Google-Smtp-Source: ALg8bN6+37aqFPNe5nY9K6UbAFLPH9ZtGciKhCZU/s52JeVA2Do/ElmAi+5xXSAjiMKNNXmBSPKHTJADSVIBHv7dHt4=
X-Received: by 2002:a81:14f:: with SMTP id 76mr4596432ywb.423.1547019645332; Tue, 08 Jan 2019 23:40:45 -0800 (PST)
MIME-Version: 1.0
References: <CAOEezJRwe9iSbGyBfyHNPn8=2avo6bAoFY56++HLY5+FZHhWgw@mail.gmail.com> <4647.1547019229@turing-police.cc.vt.edu>
In-Reply-To: <4647.1547019229@turing-police.cc.vt.edu>
From: Viruthagiri Thirumavalavan <giri@dombox.org>
Date: Wed, 09 Jan 2019 13:10:34 +0530
Message-ID: <CAOEezJSs11cRRd8xYu4TwO1Viayy8CB3-MdAicEKaJRgyn0tdg@mail.gmail.com>
To: Valdis Kletnieks <valdis.kletnieks@vt.edu>
Cc: ietf-smtp@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006bc5d1057f0194c2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/DesddoYbrZtulWIQpIwcjUfcu6Y>
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:40:48 -0000

>
> What happens if my mail server doesn't support markdown?


That's why I'm proposing the MARKDOWN extension. MARKDOWN command should be
presented in the EHLO response only if your server supports markdown.

If your server supports markdown, the mail will be transferred as
text/markdown. Else mail will be transferred as "text/plain" and
"text/html" as usual.

I hope I understood you correctly.

On Wed, Jan 9, 2019 at 1:03 PM <valdis.kletnieks@vt.edu> wrote:

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


-- 
Best Regards,

Viruthagiri Thirumavalavan
Dombox, Inc.