IETF Logo Mail Archive

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

"John R Levine" <johnl@taugh.com> Fri, 11 January 2019 21:24 UTC

Return-Path: <johnl@taugh.com>
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 EAC4C128B14 for <ietf-smtp@ietfa.amsl.com>; Fri, 11 Jan 2019 13:24:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=tNsttCco; dkim=pass (1536-bit key) header.d=taugh.com header.b=aspUGRiJ
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 8kDUJhEXVE4U for <ietf-smtp@ietfa.amsl.com>; Fri, 11 Jan 2019 13:24:32 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 49436127AC2 for <ietf-smtp@ietf.org>; Fri, 11 Jan 2019 13:24:32 -0800 (PST)
Received: (qmail 5182 invoked from network); 11 Jan 2019 21:24:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=143b.5c39098f.k1901; bh=0ivbZyUReKAdqDo8/OO8dtBBb8VxNEQLPMyhX0gDKQs=; b=tNsttCcoqAkQ9JqypQGczBgVSvc3AO2an3DX0Yzuv87/ZokEQBdJBH2PeISpUkyFsNVWEORSFIkBmXyKYn93607rXt8ULrbeY+hHgfaMYnPug4z62R7sx1Y3d0xlodCIp6L9XrIoN1tGEe4q3RBmEPp4Ln6pUuDIWmJ1QTbG54KQAe4nCbs0uaKgRgbm8dimh4vVTf4khIlcTzV+mJBzIPrE0VJrwGWbPdoKCiynXnnOdXOkyeBzvk18S6V4hq7E
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=143b.5c39098f.k1901; bh=0ivbZyUReKAdqDo8/OO8dtBBb8VxNEQLPMyhX0gDKQs=; b=aspUGRiJX+yYOj34snXQcoeQ1HnkHRWkgXIHJEjnCl/zt4OCDN9NTqTlwyu8cuXSVjXWvSgh60TgT/q0Sy9v+USgWm7WcQxlIAKp56okigACGwwkMPvHciAhmM7EI/Y07WyuXMfFO2qUzep2Wzb2RYe7K5Mj3I/U8j72Qqe3xjnn8jFyepmP3q1Ufhu6GFMF/uAxOM4U956+UFmqUT53Ok3VeDD7zImjphea1KSAyCU8+CczIabjZiR53Ee35U8K
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 11 Jan 2019 21:24:31 -0000
Date: Fri, 11 Jan 2019 16:24:30 -0500
Message-ID: <alpine.OSX.2.21.1901111624090.22582@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Gene Hightower <gene@digilicious.com>
Cc: John Bucy <jbucy@google.com>, ietf-smtp <ietf-smtp@ietf.org>
In-Reply-To: <0f692ab9-c71c-8c15-b3e1-e151c357477a@digilicious.com>
References: <CAOEezJTxTN9x_JFXgLidj9k8NVgFTRyqyQc4Aak8UEQuvjiM0w@mail.gmail.com> <20190109143529.33122200C76CAD@ary.local> <460d4589-5517-3762-5764-7474523dd09b@digilicious.com> <01R1U95VCAHI00004L@mauve.mrochek.com> <74e22977-8ee8-c762-4882-b56e5911430e@digilicious.com> <CALui8C2qzp_jBo=YHA+XXBGF6+jigDeEaX24L2bohQBdaXKHwg@mail.gmail.com> <alpine.OSX.2.21.1901101442230.18680@ary.qy> <CALui8C1FHhq0Bc1GOXe1xQ+w5c7td3BuOEhBmB6Jf0DZbXLYXw@mail.gmail.com> <alpine.OSX.2.21.1901101541030.19026@ary.qy> <0f692ab9-c71c-8c15-b3e1-e151c357477a@digilicious.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/MMFaJiNNCt7NJXe_3rvyJd8EWwo>
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: Fri, 11 Jan 2019 21:24:34 -0000

On Fri, 11 Jan 2019, Gene Hightower wrote:
>> Rather than do that, I'd rather do different duct tape that stores
>> the giant blob on an external server via soemthing like drive, box,
>> or dropbox, and puts a message/external-body part into the message.
>> See RFC 2017.
>
> Or the MTA could sore it.  Make it available via some URL that can be
> forwarded.  No need for support in the MUA if the MTA can do it.

Yeah, I think I've seen MTAs that do that.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email