IETF Logo Mail Archive

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

Viruthagiri Thirumavalavan <giri@dombox.org> Wed, 09 January 2019 14:55 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 6AA3D130E46 for <ietf-smtp@ietfa.amsl.com>; Wed, 9 Jan 2019 06:55:59 -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, 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 gurx01RCAjxF for <ietf-smtp@ietfa.amsl.com>; Wed, 9 Jan 2019 06:55:57 -0800 (PST)
Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (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 7BEF2130E69 for <ietf-smtp@ietf.org>; Wed, 9 Jan 2019 06:55:57 -0800 (PST)
Received: by mail-yb1-xb2b.google.com with SMTP id a190so3086266ybg.3 for <ietf-smtp@ietf.org>; Wed, 09 Jan 2019 06:55:57 -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=vHn7XiREgTiOZGe5afDXyVCtFyIeqWpK/nVR2La1YUI=; b=gr1Yr0gMLDf5a/Du5TS+nIgO9QXAPu5YFZs1pxYZtLG4kmIIrSY4dqPIzTttUlPdV+ /3rhlzTVJZhdS+rAw1ozwY7rKeZQ8Le+isMWKyHExdHjTH1kqQ8Lg3wgUaD/3t62v4i5 zKrFud9pK7SlpkhyWAd7OMPntxsvkw2MeZmN9igkqj1RmfvwotnbXGc+JmZmuD3p5lT2 owSE+OgW8DsxlVZvifIy+osy+AUzW4twDOwVytqxRGzaOyECKNIsV9vI1Nx9bnTzA1rw YNZJV6lMTd6aRp+CZEr5yKnjq1dJ53Sql0ZDiutZ/6bCxwK5ENCkx/3ceVOGfPQKknAd Y61Q==
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=vHn7XiREgTiOZGe5afDXyVCtFyIeqWpK/nVR2La1YUI=; b=FfEVfPkcOtgmO2R3+dMAdgnb1KhvLw7AYmZT6zh7qEIRDgiqbSCqJ8MdsL3UhYQb/C /KlBgnlYE9ydxT0vKCs8KbSF3Y/KQuPQp2Da2GwCS4a4S4S0lghqHXt0Dfe9ky+MHTHM gkt+rNSKsyF+y1cFq5kbShitjYwE6XmdhNHEqTxqqZ0WM4S3mvIX4GBXaeRFVzxL4gBb Z2x7DGgs1DbxhZENK8mPK04Y7V8w/2ixxchQzy6B/Tf3DbzhjoYp/K8sRCLoVk3/2gjW xVWkEoDpqzojjHUWxTd2iDW15HGH3Z5N7aa9AcdVkwu6dE/eEX3GmKzoU9eFeZL0cLbL rBlQ==
X-Gm-Message-State: AJcUukfnKLH6omCpzZfLvC+QdVNLyUvRaxnPZI8ZvTtnbPMKv+8+g75E Rly/N5a5qg3qNdfcBjL1U7WuKtPRFOega19Xr5SPqA==
X-Google-Smtp-Source: ALg8bN79AqzAWpGlwNb/XyeIIoxRUPUxqquOPD+LxOODkJrBRUgMOFAIpZ792wg2DUP+PvEQTD+/z461zShGHqNlf78=
X-Received: by 2002:a25:bac2:: with SMTP id a2mr5976705ybk.519.1547045756317; Wed, 09 Jan 2019 06:55:56 -0800 (PST)
MIME-Version: 1.0
References: <CAOEezJTxTN9x_JFXgLidj9k8NVgFTRyqyQc4Aak8UEQuvjiM0w@mail.gmail.com> <20190109143529.33122200C76CAD@ary.local>
In-Reply-To: <20190109143529.33122200C76CAD@ary.local>
From: Viruthagiri Thirumavalavan <giri@dombox.org>
Date: Wed, 09 Jan 2019 20:24:19 +0530
Message-ID: <CAOEezJR-EoqyH7Qfo_cTQ0r9YUvKRyJeFY2t6Wk7T88mETJhSw@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: ietf-smtp@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c1cba3057f07a837"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/WzrGVmtBLYwPIiXeDx3PtqG5lLQ>
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:56:01 -0000

Ok Thanks John.

I'll take a look.

On Wed, Jan 9, 2019 at 8:05 PM John Levine <johnl@taugh.com> wrote:

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


-- 
Best Regards,

Viruthagiri Thirumavalavan
Dombox, Inc.

v2.23.0 | Report a Bug | By Email