IETF Logo Mail Archive

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

John R Levine <johnl@taugh.com> Tue, 30 March 2021 16:00 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 683373A198A for <ietf-smtp@ietfa.amsl.com>; Tue, 30 Mar 2021 09:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=b2oftcAK; dkim=pass (2048-bit key) header.d=taugh.com header.b=TiXqMQBY
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 Hal7D1Uht9it for <ietf-smtp@ietfa.amsl.com>; Tue, 30 Mar 2021 09:00:43 -0700 (PDT)
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 8868A3A198B for <ietf-smtp@ietf.org>; Tue, 30 Mar 2021 09:00:43 -0700 (PDT)
Received: (qmail 48637 invoked from network); 30 Mar 2021 16:00:41 -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; s=bdfa.60634b29.k2103; bh=aPIoxffRf6YTk+njwbgA8l3Eo3IfwzvGJ4HuE0AF5Ws=; b=b2oftcAKGpQncZrsJq+B7epAJThOxBTQwuMUDSIIQTvNp2eOlT1qOBEznDkZyiN8SceF+Qjntz9Ew0GYKti9hfycDAGE004BbFj/pCieymhb6Jy6DF+zPbugoAcKvdV4PiT/jiro1Y03+ZfHOHttXv5toX6kLX8iXtUxuKsKdXwAKHJijCDrEy6owQMzAxNKJvMP7xeZFAn2tv3MV9xQ1DYGGGC5kqLTkRudvSNFvCJBUqxkyZZo63atVScRIEUgIfdsph5AcxFYIEWUgr3uSugbfi1n6hpX+yZk3pYnc6gIRgS1XMqD4BuzYMlS+q/fNh4iE6E1jKwo6NVIi3+RBA==
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; s=bdfa.60634b29.k2103; bh=aPIoxffRf6YTk+njwbgA8l3Eo3IfwzvGJ4HuE0AF5Ws=; b=TiXqMQBYUJ3tgAD42/P3bRzUgUCLcklT9C29/mw4TIpKBXhYNRaLTu/OaI6iKY3kwnGbSvAOsrQmP3/YJztp+6XSok2nVIY0I+nGm4KGFyyhdztNJ2Ea2hpC5a0R3e7D8qHtw28W1EJ6eE4xN8o0SeUvOqFhA2po/0VY6x2GtfJJz0GB0uUrn+4KqU+OE0otJzYZqM8PyyIRelirKQKsxL2veXwnJDiRZBpeq+XwKTf507aUYWTQJirsU5Nah28FScR9FgzYtxRMSB1em4PpTiA5mvmnGYdLblsaKIhP/q9EeAi6MpJG4rZdaKTNF7rXBMR43UK2c5O89BTqLWz66g==
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 ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 30 Mar 2021 16:00:41 -0000
Received: by ary.qy (Postfix, from userid 501) id 02CB07197487; Tue, 30 Mar 2021 12:00:40 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id AC1927197469; Tue, 30 Mar 2021 12:00:40 -0400 (EDT)
Date: Tue, 30 Mar 2021 12:00:40 -0400
Message-ID: <c23583b4-f69b-41c5-a74c-9aab697634dd@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Ned Freed <ned.freed@mrochek.com>
Cc: ietf-smtp@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <01RX9R37H1CC0085YQ@mauve.mrochek.com>
References: <cone.1617061398.771367.57281.1004@monster.email-scan.com> <20210330010027.F13AD718E3C0@ary.qy> <01RX9R37H1CC0085YQ@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/4y2uaYM_e3qY19n6MjytOfszJIk>
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: Tue, 30 Mar 2021 16:00:49 -0000

> Nope. MIME was carefully designed to support both 8bit and binary format. We
> briefly considered defining the necessary transport - and in hindsight not doing
> so was an error - but back when RFC 1521 and 1522 came out the situation
> surrounding 8BITMIME was unclear, so we didn't pursue it.

For binary parts you just scan for --delimiter\r\n ?  I guess that would 
work.

>> The advantage of BDAT over DATA for 8BITMIME is pretty modest, and can
>> even be negative for the implementations that send small 8K BDAT
>> chunks.
>
> Acutally, the advantages can be quite significant client-side, depending
> on your implementation.

I see how you could use sendfile() to blat a message to a socket if it's 
stored with \r\n line endings.  Is it more than 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