IETF Logo Mail Archive

Re: [Emailcore] Delivered-To issues

Jeremy Harris <jgh@wizmail.org> Sat, 02 January 2021 22:41 UTC

Return-Path: <jgh@wizmail.org>
X-Original-To: emailcore@ietfa.amsl.com
Delivered-To: emailcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABB6A3A0EFC for <emailcore@ietfa.amsl.com>; Sat, 2 Jan 2021 14:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=wizmail.org header.b=aZWTFOvI; dkim=pass (2048-bit key) header.d=wizmail.org header.b=ZHgG3AFf
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 q7t23PZm5H-s for <emailcore@ietfa.amsl.com>; Sat, 2 Jan 2021 14:41:53 -0800 (PST)
Received: from wizmail.org (wizmail.org [IPv6:2a00:1940:107::2:0:0]) (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 EBD3F3A0EFA for <emailcore@ietf.org>; Sat, 2 Jan 2021 14:41:52 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; q=dns/txt; c=relaxed/relaxed; d=wizmail.org; s=e202001; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:Subject:From:References:To:From: Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive:Autocrypt; bh=HxKYRyGh44ERAgY7oEq/ZgjtcI3a7OkvnnE7JAQqnZ8=; b=aZWTFOvI409oVLJ8aj0DhNvDPe XUPD5vYHAN2C4svlH6Ye5Ism4f5ay18RwQ9UXTKi5X7GPqaKYKF85+slBzCg==;
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=wizmail.org ; s=r202001; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:Subject:From:References:To:From:Sender:Reply-To: Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive:Autocrypt; bh=HxKYRyGh44ERAgY7oEq/ZgjtcI3a7OkvnnE7JAQqnZ8=; b=ZHgG3AFfXUfnab18Cm9CypZMmb CtFxM0IlCHQ459X5Df8ZQs67vt6kowMcirDQmjlC6orcT+W2SBxUgxGupuKINid96Zzpl4KsmO5pS IQ1eW7MchnleuNBr67juY+hb98TjFCqqJ8AA17hW/vOckE/InJpGWBBQgLXW+ai+l6Ov54JaWPCHo EPyihjVBzHer9VVE2wZaCwefZlaGENpnLLB+BPEVPLjevZNHf9m15CJtmRE+wUV1cs5tBkfdFsRoZ 4shIrF7IfOtByka5C2CY16y4tgCSqEmIKJA5Gyvnc8HfLmsDNb45EMbvOP7FtZduM/LE1bw3b4+3P ZqyPPFPw==;
Authentication-Results: wizmail.org; iprev=pass (vgate18.wizint.net) smtp.remote-ip=2a00:1940:107::1:2f:0; auth=pass (PLAIN) smtp.auth=jgh@wizmail.org
Received: from vgate18.wizint.net ([2a00:1940:107::1:2f:0] helo=lap.dom.ain) by wizmail.org (Exim 4.94.110) (TLS1.3) tls TLS_AES_128_GCM_SHA256 with esmtpsa id 1kvpap-008h8F-7z for emailcore@ietf.org (return-path <jgh@wizmail.org>); Sat, 02 Jan 2021 22:41:51 +0000
To: emailcore@ietf.org
References: <20210102222659.E290E4A396E1@ary.qy>
From: Jeremy Harris <jgh@wizmail.org>
Message-ID: <11d3fbf3-b5e9-b876-88d0-6e60465e070b@wizmail.org>
Date: Sat, 02 Jan 2021 22:41:50 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210102222659.E290E4A396E1@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-Pcms-Received-Sender: vgate18.wizint.net ([2a00:1940:107::1:2f:0] helo=lap.dom.ain) with esmtpsa
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/7nj3WozUcZAJdQUEa5wKEood4ts>
Subject: Re: [Emailcore] Delivered-To issues
X-BeenThere: emailcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EMAILCORE proposed working group list <emailcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emailcore>, <mailto:emailcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emailcore/>
List-Post: <mailto:emailcore@ietf.org>
List-Help: <mailto:emailcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emailcore>, <mailto:emailcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jan 2021 22:41:55 -0000

On 02/01/2021 22:26, John Levine wrote:
> In article <f6399eaa-ec58-bfeb-e232-0646df41a979@wizmail.org> you write:
>>> Should we be defining both, making it clear that they are
>>> different, and then making whatever recommendations seem
>>> appropriate about which one (or both) should be provided?
>>
>> I agree that Envelope-To: and Delivered-To: are different.
> 
> Agreed.  What's the difference between Envelope-To and the
> FOR clause in a Received header?

Exim ducks, and only includes a "for" clause in the Received:
for single-RCPT messages.

On the other hand, a message which is (locally) aliased to
more than one destination name, which are then further aliased
to a single final name - will (assuming env-to was configured)
get an Envelope-To: with multiple copies of the RCPT.
-- 
Cheers,
   Jeremy

v2.23.0 | Report a Bug | By Email