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

"John Levine" <johnl@taugh.com> Wed, 16 January 2019 21:16 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 8AB9F13117C for <ietf-smtp@ietfa.amsl.com>; Wed, 16 Jan 2019 13:16:26 -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=M2AMrK6P; dkim=pass (1536-bit key) header.d=taugh.com header.b=lS9jqlZu
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 jx_J8wJN5_PL for <ietf-smtp@ietfa.amsl.com>; Wed, 16 Jan 2019 13:16:25 -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 140951292F1 for <ietf-smtp@ietf.org>; Wed, 16 Jan 2019 13:16:24 -0800 (PST)
Received: (qmail 27063 invoked from network); 16 Jan 2019 21:16:23 -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=69b5.5c3f9f27.k1901; bh=yY5bvPsjeyw3Qj+/6zRJpN68rImERIFxRRh0cnKbYMM=; b=M2AMrK6PCRRimd9ggMTSNtbEB3p5zHa7wvS/tz7eG/TrDKoUFbMg22+AcYmc6XsF74mFYtA/gZhnUclbZd9Gnc4BhbWZIxup64boEopi4uqzdR5hyUKIBwFUyOwxifY8tIfaJ2GPzDQfF+WzXOgbABkLTAuzfsGIIVUn3Ld3e4/Vw1ZwvswAH/HdqINM5IGYpxk+PzodEsDcZWgAJOD/riIgYDAlINoDIXmbuq+SffZcnewC59dNGuGIiynTZEB8
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=69b5.5c3f9f27.k1901; bh=yY5bvPsjeyw3Qj+/6zRJpN68rImERIFxRRh0cnKbYMM=; b=lS9jqlZuV55s11pf+4q17g95iSZrs3JCmokt4FJxBCh75KNIDfdzAAiAh6w2bb2gLOxdGxARtRC0siT4xce7YJbCHobFFT6FA6FxSuYLsDqxP9aJ+bdVR8FqIkoDD51G+DjaKXNalslm9d8mbBjrs7FRW6wJOijE26ml8hElgLWha4uUyPvWbcMNmFwzY+OwG6NOM1IRmVQkPiHafRBVpSDitsUNukcve9u4qqedQv9fwW8S6FKsgSDvXXdW4pmX
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; 16 Jan 2019 21:16:23 -0000
Received: by ary.qy (Postfix, from userid 501) id 209FC200CC3BD1; Wed, 16 Jan 2019 16:16:22 -0500 (EST)
Date: Wed, 16 Jan 2019 16:16:22 -0500
Message-Id: <20190116211623.209FC200CC3BD1@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: jgh@wizmail.org
In-Reply-To: <0826bb60-8ebb-f531-2a1d-8fad91335ff1@wizmail.org>
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/40H83VizWIDOfUg7WKiHGVt7d9w>
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: Wed, 16 Jan 2019 21:16:27 -0000

In article <0826bb60-8ebb-f531-2a1d-8fad91335ff1@wizmail.org> you write:
>On 16/01/2019 20:02, Gene Hightower wrote:
>> On 16/01/2019 11.15, Jeremy Harris wrote:
>>> Efficiency.  Not having to do dot-stuffing means that sendfile etc.
>> 
>> Can you use sendfile() after STARTTLS?
>
>I'm not aware of the common TLS libraries providing an equivalent
>interface yet, but once the symmetric-crypto portion is established
>in the kernel I'd think it possible.  Perhaps five years from now?

Even if someone puts some of the crypto glop in the kernel, the
benefit of sendfile() is minimal.

The point of sendfile is that the kernel can send network data
directly from the disk buffer.  That's never going to happen if it has
to be encrypted first.  If it has to read the buffer, encrypt it, and
put it back, that's just like copying it while encrypting.

Either way, it seems like a pretty minor optimization.  My MTA
routinely has a hundred connections going at once and it's totally I/O
bound.

R's,
John