IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Thu, 10 January 2019 19:15 UTC

Return-Path: <johnl@iecc.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 A93C8130F88 for <ietf-smtp@ietfa.amsl.com>; Thu, 10 Jan 2019 11:15:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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=HraPgPee; dkim=pass (1536-bit key) header.d=taugh.com header.b=bskfFzU1
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 i5CpQ7fRdqyi for <ietf-smtp@ietfa.amsl.com>; Thu, 10 Jan 2019 11:15:13 -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 AC863130F34 for <ietf-smtp@ietf.org>; Thu, 10 Jan 2019 11:15:13 -0800 (PST)
Received: (qmail 38204 invoked from network); 10 Jan 2019 19:15:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=9537.5c3799c0.k1901; bh=ccItDnnc3hIE+oL1WTq/jX3jEtQ+VD5rWZ3J5Z2OlM8=; b=HraPgPee11uhv1I/iddLFM9wz/6/lvGH+WqHFwbkCLEhZQW4TvCtaj1pyew0uS2FDQ/9bJxlPeHbXkUEMBsaa8pZBPjg+R1zaceoY202BfQLLGoEzjpd7hknT/JfyqgawPEQbbC5uE2fMQyAsGT9chYePJ+v5s063/UnyF7GcvIJy0EkBpjMxwgX6b5qg3E6eNfUZdxU7l6+OPGQoovcx3eZY436SJbPXltRNbIpisIskWbiYM/EbvZciMhPlWmF
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=9537.5c3799c0.k1901; bh=ccItDnnc3hIE+oL1WTq/jX3jEtQ+VD5rWZ3J5Z2OlM8=; b=bskfFzU10r9zjcrH85dUHTgP9ffy+wqRP3dLWDvrbtzr8hZcpTKJEqseYaNjaJO6EvDigqlOyOtrYce9l8LePXoFwuOdkSs3p1uW7mQNjzo5rrAwikSpk3gOYjP5NjwATzGaJD+s6DSCv09AFMzM8r/uuZKea9825DTQOIoGJPdFUqmsITU/CuRwzVxRoEECMc9UEsdOCYk2uLlcMxijlPqcpIZSJexYX1t27355A3o6gjfetyyjoNwV5zx9uDVU
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 10 Jan 2019 19:15:12 -0000
Received: by ary.qy (Postfix, from userid 501) id 6F197200C830C9; Thu, 10 Jan 2019 14:15:11 -0500 (EST)
Date: Thu, 10 Jan 2019 14:15:11 -0500
Message-Id: <20190110191512.6F197200C830C9@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: gene@digilicious.com
In-Reply-To: <74e22977-8ee8-c762-4882-b56e5911430e@digilicious.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/Pfcx4rdtLGK09xzWDD1GnrzBRdg>
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:15:16 -0000

In article <74e22977-8ee8-c762-4882-b56e5911430e@digilicious.com> you write:
>Question is, is BINARYMIME doable?  Or a lost cause?

After 18 years, I think the answer should be obvious.

At modern network speeds, base64 encoding is good enough for the file
that people attach to mail messsages.  If you have something big
enough that BINARYMIME would make a difference, sensible people use
something like dropbox and send a link.

-- 
Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email