On 4/14/2022 1:27 PM, John Levine via mailop wrote:
Is anyone aware of any mail system that implements Delivered-To
the way this document describes,
Your query, to this list arrived at my inbox with these header fields:
Return-Path: <mailop-boun...@mailop.org>
Delivered-To: d...@dcrocker.net
Received: from mx.mailop.org (mx.mailop.org [91.132.147.157])
by gcp-europe-west4-b-smtpin5.hostinger.io (mx.hostinger.com) with
ESMTPS id 4KfWJZ1H9Sz9v9X5
for <d...@dcrocker.net>; Thu, 14 Apr 2022 20:29:02 +0000 (UTC)
...> Date: 14 Apr 2022 16:27:53 -0400
Message-Id: <20220414202755.aee5f3dac...@ary.qy>
To: mailop@mailop.org
In-Reply-To: <eb44c0a6-8ebb-70f2-e211-4be7e6361...@dcrocker.net>
Organization: Taughannock Networks
...
List-Id: For mail operators <mailop.mailop.org>
List-Unsubscribe: <https://list.mailop.org/options/mailop>,
<mailto:mailop-requ...@mailop.org?subject=unsubscribe>
List-Archive: <https://list.mailop.org/private/mailop/>
List-Post: <mailto:mailop@mailop.org>
List-Help: <mailto:mailop-requ...@mailop.org?subject=help>
List-Subscribe: <https://list.mailop.org/listinfo/mailop>,
<mailto:mailop-requ...@mailop.org?subject=subscribe>
From: John Levine via mailop <mailop@mailop.org>
Reply-To: John Levine <jo...@taugh.com>
if that does not conform to the RFC's specification, please explain how.
rather than for loop breaking
with a token that looks like a mailbox but isn't?
Since there has been no claim or expectation that the field already has
deployed use beyond loop-detection and, in fact, the RFC explicit states
that that larger role is one of the reasons it was issued as
Experimental, your query is a bit odd.
d/
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
