Re: [ietf-smtp] Quoted-Printable-8bit

Viktor Dukhovni <ietf-dane@dukhovni.org> Wed, 31 March 2021 02:09 UTC

Return-Path: <ietf-dane@dukhovni.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 AFAD83A113A for <ietf-smtp@ietfa.amsl.com>; Tue, 30 Mar 2021 19:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 cpX7qjc_MyCf for <ietf-smtp@ietfa.amsl.com>; Tue, 30 Mar 2021 19:09:55 -0700 (PDT)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (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 6FE9C3A1138 for <ietf-smtp@ietf.org>; Tue, 30 Mar 2021 19:09:53 -0700 (PDT)
Received: by straasha.imrryr.org (Postfix, from userid 1001) id 11CF4D92C7; Tue, 30 Mar 2021 22:09:52 -0400 (EDT)
Date: Tue, 30 Mar 2021 22:09:52 -0400
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf-smtp@ietf.org
Message-ID: <YGPZ8FiHweZHP4z6@straasha.imrryr.org>
Reply-To: ietf-smtp@ietf.org
References: <20210330220929.DCC8F71A5097@ary.qy> <A490D3D79A3AA02E477D0611@PSB> <46d82824-d395-d816-cb8d-e5f24af58282@taugh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <46d82824-d395-d816-cb8d-e5f24af58282@taugh.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/0pwe6Z2C1FOXYTKwJWMIXGvlR-8>
Subject: Re: [ietf-smtp] Quoted-Printable-8bit
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, 31 Mar 2021 02:09:57 -0000

On Tue, Mar 30, 2021 at 08:39:03PM -0400, John R Levine wrote:

> I couple of years ago I did some surveys of MTAs for the UASG.  Of 56,901 
> MTAs I survyed, 56,262 advertised 8BITMIME.  The only identifiable MTA not 
> offering it was an obscure Windows MTA called Mailenable.
> 
> There were a few Postfix and Exim servers not advertising it (165 out of 
> 28,000 for Exim, 15 out of 14,739 for Postfix) which I assume were 
> configuration errors.
> 
> It would be resonable to make 8BITMIME a MUST now.  Ever since the last 
> PDP-10 left the net about 30 years ago, every machine on the Internet uses 
> 8 bit bytes which makes 8BITMIME close to free to implement.

Not much point, unless one also at the same time deprecates 7bit
downgrade when the peer does not advertise 8BITMIME.  Otherwise, the
behaviour when it is a MUST is indistinguishable from the status quo.

Are you proposing that too?  I believe most user-friendly MUAs send
quoted-printable, so the issue is typically moot.  Though "mutt",
which I am using for this message, does send unencoded UTF-8 as an
8bit body (I have send_charset="us-ascii:utf-8:iso-8859-1").

-- 
   Виктор.