IETF Logo Mail Archive

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

"John R Levine" <johnl@taugh.com> Thu, 10 January 2019 19:48 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 85BD3131236 for <ietf-smtp@ietfa.amsl.com>; Thu, 10 Jan 2019 11:48:24 -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, SPF_PASS=-0.001, URIBL_BLOCKED=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=oDj9TJKP; dkim=pass (1536-bit key) header.d=taugh.com header.b=cQA0MOJ4
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 KQgiSlDdHbWV for <ietf-smtp@ietfa.amsl.com>; Thu, 10 Jan 2019 11:48:22 -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 A9B14130F88 for <ietf-smtp@ietf.org>; Thu, 10 Jan 2019 11:48:22 -0800 (PST)
Received: (qmail 43973 invoked from network); 10 Jan 2019 19:48:20 -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=abc3.5c37a184.k1901; bh=MlKvSAqseym0sdTp2iprDWHz7kalCD97CHKH44iabJI=; b=oDj9TJKPgH47aIfJbBY0EK90Yo24V/KJtCGbR40MTFA+fS5R+hJZCF+6eY/Ds5n5qrB4b9ukN/mgE4mAXJvjksWxjoioI/KUs2mIBuFe0QGrThSojwqm55kIvuL2uA/+DC/fGd4h9J+H3xGwa3gVywZ0dwG6kGJxGXspmGKDxIJdEcbL+Sf4pfhUL9cqmrpihL1dFHTNgdetu2E9JgTghhMBnQtGJr4Q8JTJMM2L8MyUkmgBQ6U03cWyIq3u0y0p
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=abc3.5c37a184.k1901; bh=MlKvSAqseym0sdTp2iprDWHz7kalCD97CHKH44iabJI=; b=cQA0MOJ4bWqoCzFwKR86dVQEixv6JsycmXK/G/ZZff7IFb2lQyx9XdzHUPGqAkrP16iJpoA7hozPQ96JKapeSJ8zH9sxecjvt0oS58gL7Ibay3BpVuN4mOCQMfCIJ3qtBYPDhp7DicZlK2d4F5desqyDBhPLG37X/uHtmPLg+7dAWISTn8JQV2bVkdmeLq7jfRtzZox8s+OiSy2eCU6sfbAaLIdYAQCH/RdevT4L2c6gxcWk5ntdJ4rUrcbJrXdb
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; 10 Jan 2019 19:48:20 -0000
Date: Thu, 10 Jan 2019 14:48:19 -0500
Message-ID: <alpine.OSX.2.21.1901101442230.18680@ary.qy>
From: John R Levine <johnl@taugh.com>
To: John Bucy <jbucy@google.com>
Cc: ietf-smtp <ietf-smtp@ietf.org>
In-Reply-To: <CALui8C2qzp_jBo=YHA+XXBGF6+jigDeEaX24L2bohQBdaXKHwg@mail.gmail.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>
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/LKClTpyfwZgM3ay0Ir9Hq6GDVAQ>
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: Thu, 10 Jan 2019 19:48:24 -0000

On Thu, 10 Jan 2019, John Bucy wrote:
>> Question is, is BINARYMIME doable?  Or a lost cause?
>
> As I see it, the problem is a message getting stuck "in the middle" where
> the next hop doesn't support the extension e.g. user has a .forward file.

For systems that have separate MUA and MTA, the MUA has no way to tell 
whether a downstream recipient will support BINARYMIME, and like you said, 
trying to recode on the fly causes more problems than it solves.

I see that Gmail has a 25M message size limit, which allows an 18M 
attached file encoded in base64.  If you supported BINARYMIME so the 
attached files could be 24M, would anyone care?

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