IETF Logo Mail Archive

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

Peter Bowyer <peter@bowyer.org> Wed, 09 January 2019 08:42 UTC

Return-Path: <peter@salmark.co.uk>
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 0BBEC130934 for <ietf-smtp@ietfa.amsl.com>; Wed, 9 Jan 2019 00:42:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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 0shwr3jeXnil for <ietf-smtp@ietfa.amsl.com>; Wed, 9 Jan 2019 00:42:01 -0800 (PST)
Received: from mail-wm1-f47.google.com (mail-wm1-f47.google.com [209.85.128.47]) (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 636E6128766 for <ietf-smtp@ietf.org>; Wed, 9 Jan 2019 00:42:01 -0800 (PST)
Received: by mail-wm1-f47.google.com with SMTP id y139so6643089wmc.5 for <ietf-smtp@ietf.org>; Wed, 09 Jan 2019 00:42:01 -0800 (PST)
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; bh=z3tGY7OwAFbDS15albGjKKI+A7/zP6teO62qDEDJ38s=; b=ECrEC3x8tzjC7M18M5V2OOxwsp6YTkqSzXBDYIGukpgBrbTz5fHmsD0Wf3lL7BWULk iu2pOQNzNcfnqcrMrsQWsCx/T+iXbPSFoYglKzGjOtz7oyzs6fU4E3p1BRXfx631Gsdk qFGgRP+K4sQdhVDtyp5lA8V3My80kJ1KXI4DONf4BBk2cSFP/OaOr0VhHhk6EiSaAf1a /lXwlxdRSCzFUijfljWv2ammJJvH+6lMEuqiPSFEUCj7zX8Oa+49BoY7oHA+ex2DWQ5Q ml2U7L1CiBUgUgHCUTFqN9crkfAYNEhxGkaNQbuZSNVgTEbklbyRCi7ReiB6RVb9Q3FI nuzg==
X-Gm-Message-State: AJcUukek+LfS1lRhusVyJ0Yhrt6MRedMBZw84Ni13nClGo/MS4y+3J4A 4yPZ3/HvjOvvvns0oUKWqKU8w5FOBr3vzGD1M/1mvFX1jW4=
X-Google-Smtp-Source: ALg8bN76X/NAfEI4s2X8tPfygoDAQ8iLPMCdcFmpB5RMbkrhPf5zHPltqKePluNkkNb7vPt0MctBhbicAykolX6Rh98=
X-Received: by 2002:a7b:c92d:: with SMTP id h13mr4492429wml.96.1547023319057; Wed, 09 Jan 2019 00:41:59 -0800 (PST)
MIME-Version: 1.0
References: <CAOEezJRwe9iSbGyBfyHNPn8=2avo6bAoFY56++HLY5+FZHhWgw@mail.gmail.com> <4647.1547019229@turing-police.cc.vt.edu> <CAOEezJSs11cRRd8xYu4TwO1Viayy8CB3-MdAicEKaJRgyn0tdg@mail.gmail.com>
In-Reply-To: <CAOEezJSs11cRRd8xYu4TwO1Viayy8CB3-MdAicEKaJRgyn0tdg@mail.gmail.com>
From: Peter Bowyer <peter@bowyer.org>
Date: Wed, 09 Jan 2019 08:41:47 +0000
Message-ID: <CAGfapNN4Vx5nffPj=hcd9oLmYrRY7CEJna51G=wEmUhGvfbzAg@mail.gmail.com>
To: ietf-smtp@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/GBQlIHeqkhttDEtVQSXs7umAluo>
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 08:42:05 -0000

On Wed, 9 Jan 2019 at 07:40, Viruthagiri Thirumavalavan <giri@dombox.org> wrote:

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

What piece of the *server* has to support markdown? The content of the
message isn't the server's business. Nor is knowing what content
type(s) are acceptable to each final destination for each recipient of
each message in a session. That's a matter for the originating MUA and
the receiving MUA to worry about. The server's job is to move the
(mostly) opaque content from one to the other.

PB

v2.23.0 | Report a Bug | By Email