IETF Logo Mail Archive

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

Gilles Chehade <gilles@poolp.org> Wed, 09 January 2019 07:44 UTC

Return-Path: <gilles@poolp.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 C030412F1A2 for <ietf-smtp@ietfa.amsl.com>; Tue, 8 Jan 2019 23:44:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.999
X-Spam-Level:
X-Spam-Status: No, score=0.999 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, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=poolp.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 lErVWpCcL1h5 for <ietf-smtp@ietfa.amsl.com>; Tue, 8 Jan 2019 23:44:37 -0800 (PST)
Received: from out.mailbrix.mx (out.mailbrix.mx [212.83.129.132]) (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 72E47128766 for <ietf-smtp@ietf.org>; Tue, 8 Jan 2019 23:44:35 -0800 (PST)
Received: from poolp.org (localhost [127.0.0.1]) by poolp.org (OpenSMTPD) with ESMTP id 3300a2ca; Wed, 9 Jan 2019 08:44:32 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=poolp.org; h=date:subject :message-id:in-reply-to:from:to:cc:mime-version:content-type :content-transfer-encoding; s=opensmtpd; bh=gHqbs12Jp4NCY+p2zX3n gEJQCAs=; b=U9igaZ/IqzmmGvWPv0CdLvNmNYb5IaNwAQk1ulY24shAJr2BmUWH JijcrrxIpCuDkPXUqWo1oFUlCBKhy/XyzHI3tHKy88kj7c+oIP81gNeCXNt/Y8PB JPMilKBHcgK0ls66fYR0uEf1oC67S/ERkrPwLIZUfvMdYTsrM4DN2WI=
Received: from [192.168.1.12] (lfbn-1-5141-126.w90-105.abo.wanadoo.fr [90.105.116.126]) by mail.poolp.org (OpenSMTPD) with ESMTPSA id 4b3e072b (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Wed, 9 Jan 2019 08:44:32 +0100 (CET)
Date: Wed, 09 Jan 2019 08:44:26 +0100
Message-ID: <144aafd5-7468-4d55-a7b7-bead5cc67e1e@email.android.com>
X-Android-Message-ID: <144aafd5-7468-4d55-a7b7-bead5cc67e1e@email.android.com>
In-Reply-To: <CAOEezJRwe9iSbGyBfyHNPn8=2avo6bAoFY56++HLY5+FZHhWgw@mail.gmail.com>
From: Gilles Chehade <gilles@poolp.org>
To: Viruthagiri Thirumavalavan <giri@dombox.org>
Cc: ietf-smtp@ietf.org
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/HhPF4nRZt19qKFO2dIF34dICZ-U>
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:44:40 -0000

Hello,

After reading your proposal, I don't quite understand what it is about and what is expected from SMTP implementations.

The content type is part of the message, not part of the protocol, also your rationale seems to equate one SMTP session to one message but a single session may transport multiple messages with different messages with different content types.

Gilles



Le 9 janv. 2019 07:59, Viruthagiri Thirumavalavan <giri@dombox.org> a écrit :
Hello Everyone,

I'm the guy who proposed SMTP Over TLS on Port 26. Looks like that was a dead end. So, now coming with another proposal.

I joined IETF day before yesterday. So not sure if this was already discussed before and got rejected. If this was rejected already, then my apologies.

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

I listed the benefits in my proposal. Let me if it is worth going forward. So I can create an Internet Draft.


Thanks

--
Best Regards,

Viruthagiri Thirumavalavan
Dombox, Inc.

v2.23.0 | Report a Bug | By Email