Re: [ietf-smtp] encouraging PRDR (was: How to encrypt SMTP?)

Keith Moore <moore@network-heretics.com> Sun, 27 October 2019 20:39 UTC

Return-Path: <moore@network-heretics.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 9BC7B1200B1 for <ietf-smtp@ietfa.amsl.com>; Sun, 27 Oct 2019 13:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 EySvSubNIY8O for <ietf-smtp@ietfa.amsl.com>; Sun, 27 Oct 2019 13:39:33 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B20812006B for <ietf-smtp@ietf.org>; Sun, 27 Oct 2019 13:39:33 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 9CC555D3; Sun, 27 Oct 2019 16:39:32 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sun, 27 Oct 2019 16:39:32 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=22Fui+ifUvKJUBxmzNUnnYVMmerIHdPkINVn9K7ue jg=; b=QAjZzXVHIdd1odnoAbZV35lg0DCERzd+BJOczErH1rl6U3ghoHtxyVDd/ gsDJuSwj+jn+ILGmw8qdstDSJRpw+QzgE0BEiV540xIpejg3N+IIR+ZjCaYpL7aP cUP11+2koOjaGqJTIV7PO9mRRRSxAwsuzbXR4C852Oy/PG2kgs2SK1uB2WoGsfTM LJd7bd5lPZkbcqn8N2Y8XAiQ/DQgi46m4R3pR12f8IuRHdbNVL8IVMtRUid4A9D2 MYOUebPAeW+S2g4MjYCAVUg4nbTbfC0cfp9EFWCP45bekGL+OY5U5jDC2n8euNHE WvgP6EAYMuZIDZdgRsfT0GnKzWWWg==
X-ME-Sender: <xms:gwC2XU_nE8a1Lf9Je92hzsogIW5zUb9e0Td6DDzCitUWmcBySvLLjw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrleejgddugeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtke ertddtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucfkphepuddtkedrvddvuddrudektddrud ehnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghr vghtihgtshdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:gwC2XQ9sQ5h1EtpCqeVbbGjeGcOXHkbbJJS_UxlTyh4VtibcX68iHw> <xmx:gwC2XVBpSclEt1mSOisXzhLbWwxP_zOncQWRB3uw2HGnOyXIwOQVFA> <xmx:gwC2XYzAni02lCtsKZS18ICaSdhd-SGHCCIN1IdCeZaXKzu_qysvzQ> <xmx:hAC2XcktVSKDrEfXqoHd1dDMm58BCIzB6GoKS-yTEZUoC79SwFdugg>
Received: from [192.168.1.97] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 62364D6005F; Sun, 27 Oct 2019 16:39:31 -0400 (EDT)
To: ietf-smtp@ietf.org
References: <DA6C74A3-0D48-4D73-AE06-20378A5CFE54@dukhovni.org> <037312D9-E9DD-464C-89D3-036786456119@network-heretics.com> <1e101a1aeb66541e04718e90227603223ca4f33e.camel@aegee.org>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <cd435945-17f3-780b-711a-918dd76cbaf3@network-heretics.com>
Date: Sun, 27 Oct 2019 16:39:30 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <1e101a1aeb66541e04718e90227603223ca4f33e.camel@aegee.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/9tnspcwRHewStgcfPsxmwzW7jlY>
Subject: Re: [ietf-smtp] encouraging PRDR (was: How to encrypt SMTP?)
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: Sun, 27 Oct 2019 20:39:35 -0000

On 10/27/19 3:58 PM, Дилян Палаузов wrote:

> If random 4xx on MAIL as penalty for not offering reasonable TLS will help make things better, will random mail
> segmentation as penalty for senders not supporting PRDR, convince anybody to implement PRDR?

I don't think they're going to be well-correlated, because the benefits 
from encrypting mail transport and the benefits from optimizing mail 
error reporting are different.   They benefit different parties, and the 
perceived importance of encryption is different than the perceived 
importance of optimizing mail error reporting.

I support the idea behind PRDR and am not aware of any drawbacks to 
implementing it.   In general my observation is that the earlier mail 
transmission errors are caught and reported, the more reliable the 
reporting is; and the overall reliability of email improves by improving 
error reporting.

Keith