Re: [ietf-smtp] Delivered-to and Return-path

John Levine <johnl@taugh.com> Thu, 18 February 2021 16:28 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 694AE3A1409 for <ietf-smtp@ietfa.amsl.com>; Thu, 18 Feb 2021 08:28:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=V7lQDdRz; dkim=pass (2048-bit key) header.d=taugh.com header.b=tp2/9LUI
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 zaP9xZxu-ytT for <ietf-smtp@ietfa.amsl.com>; Thu, 18 Feb 2021 08:28:24 -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 376523A1405 for <ietf-smtp@ietf.org>; Thu, 18 Feb 2021 08:28:23 -0800 (PST)
Received: (qmail 65134 invoked from network); 18 Feb 2021 16:28:22 -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:cleverness; s=fe6c.602e95a6.k2102; bh=TfLrcyD5OvHvCRf0eaTokJxbpqGb1L7t43mUfb3lK+E=; b=V7lQDdRzQIs7o/leiRKH2EqobPVS1xWswYf0kZ2GNx2bKU8rsuGUKznNfitHkzBiIWkxzUcu3JYDsRslHgtw4B4RF79YRCjXbJBVTzmI7Dw5bMznVbtyt38k8xxN1qZJBIo7cnGbVHvFSu1uNOZeJgiPaPjfA5sT45bMBMQGwTaqrw1w5lRgnUCiWevRYwj0qRYg8C5g5/1lMStjUx0p6+eQPotMpFj4jY/Maq4g2+9A1P7fYo6VXQH400VRnAoQvxQmwsVs+m3BuyiXw8JIG9UtCwhmKs1CyUvhJJdYKHGpgZq8z85gKJMr7w5A7T3HbFchgWO09y2B0PQQiw7Gjw==
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:cleverness; s=fe6c.602e95a6.k2102; bh=TfLrcyD5OvHvCRf0eaTokJxbpqGb1L7t43mUfb3lK+E=; b=tp2/9LUIMy9wn7N+GH8xAKW8Zr+lBp4ivG+dIgcZK7Ilp00U7ikfYqcKsTTD9KxFvWM86N9pHdmECjP8rxu2sqMyeIhI2aTLJe3rmWushIpaRHrV84UGahGmMzm//lNYgQe1EgsYpbV9c2dZktgigaaIXT2FYhnfvdNw3vaf7V7gtUS/iUEyFOn4+luhWWu6++a5vBkhgVDGG6JSXxjkSZ5qViHalNrItJwOkLA3+PVjChm8MBGPuY0T1OaZyTSZCPjQT1E1Om1M7LZCDdwGnDJT04T74eRKRuJngU89GIF/j/2chInfyD7ViCqSn+h0jRyfDxnjoGKohh4VXgpewQ==
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; 18 Feb 2021 16:28:22 -0000
Received: by ary.qy (Postfix, from userid 501) id A79EA6E31B76; Thu, 18 Feb 2021 11:28:21 -0500 (EST)
Date: Thu, 18 Feb 2021 11:28:21 -0500
Message-Id: <20210218162821.A79EA6E31B76@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: john-ietf@jck.com
In-Reply-To: <3073462D484914E07B452E20@PSB>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
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/YdClrcrBLpj2ZbVa4mx4qyZDx20>
Subject: Re: [ietf-smtp] Delivered-to and Return-path
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, 18 Feb 2021 16:28:26 -0000

In article <3073462D484914E07B452E20@PSB> you write:
>If I correctly understand the intended use of Delivered-to and
>the meaning of "added at the time of delivery", I believe that
>the examples in Section 4 are in error. ...

The examples show long standing practice so if they disagree with the
text, the text is wrong.

It is quite common for an MTA to add Delivered-To headers as an
address is internally rewritten or forwarded without also adding a
Return-Path.  I've sent a few examples of MTAs doing that.

This is of course completely consistent with it being a trace header.

As far as loop detection, again, that's existing practice. We can
describe it, without offering advice on what we think the best loop
breaking techniques are. The MTAs that add Delivered-To also count
Received headers since there are plenty of loops that Delivered-To
doesn't catch.

R's,
John