Re: [dmarc-ietf] Fwd: New Version Notification for draft-crocker-dmarc-sender-01.txt

John Levine <johnl@taugh.com> Tue, 28 July 2020 17:41 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16A6C3A0A66 for <dmarc@ietfa.amsl.com>; Tue, 28 Jul 2020 10:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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.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=GF3QBgDv; dkim=pass (1536-bit key) header.d=taugh.com header.b=txwperV3
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 18NQpWUekZde for <dmarc@ietfa.amsl.com>; Tue, 28 Jul 2020 10:41:36 -0700 (PDT)
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 A59213A0A64 for <dmarc@ietf.org>; Tue, 28 Jul 2020 10:41:36 -0700 (PDT)
Received: (qmail 80839 invoked from network); 28 Jul 2020 17:41:35 -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=13bc3.5f20634f.k2007; bh=0bOU9/gxeTXPZUZoNx4cRumZp+/r7Z3HDfdppQByDrY=; b=GF3QBgDvgAag0Io8cHJ1Ki61HnQop3sEu6IVGjMYQ2lUAf/2KA7fxG0RagYdLynYuStfI8DI782AM04cFJN+FGe73yV2hYc/5sMjP3MVWhVX4PsINYKFY6Q5lsEKZ7r5Ywl9FEU0og+YXGZ0LOZM03izTCUdFx1xJQvJU2CX1tEoEagO2RuciN1pxx91riT03T5BhlSOcPu5FdyYriqNFFOWrjLcsHA4bJ5skyVk8yefKNUPJj73Fi5oZqFm1h0/
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=13bc3.5f20634f.k2007; bh=0bOU9/gxeTXPZUZoNx4cRumZp+/r7Z3HDfdppQByDrY=; b=txwperV3O4bY7sj1lJqxrDylgky6ni2LV3iHgI2zGzwaQbAiVa50bEshUa3m4YpU9hywDrgOplMeRhZIi9tAF75OkhExl0gsJGlba4WY9AnqMuJzOjmeouYXOI2slMcGdof0eNk2V6RMi9MnQnhxEpUlfXJ74qQiN1Xch64yvhn56B/7vRcmiXd6FfcfNI6Nn3Tf0F0uMOHYm9CnIE4qFjZLZN9UIxvSyS5zsPtulbYysQXrAI8h1yBPn1dq5ti8
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; 28 Jul 2020 17:41:34 -0000
Received: by ary.qy (Postfix, from userid 501) id 72B2A1D98455; Tue, 28 Jul 2020 13:41:34 -0400 (EDT)
Date: Tue, 28 Jul 2020 13:41:34 -0400
Message-Id: <20200728174134.72B2A1D98455@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <d034aac6-e50c-8e6b-16f1-8c41e711b837@tana.it>
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/dmarc/_D-IVgUspWX6CtgPS0yD5r3rDoc>
Subject: Re: [dmarc-ietf] Fwd: New Version Notification for draft-crocker-dmarc-sender-01.txt
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2020 17:41:38 -0000

In article <d034aac6-e50c-8e6b-16f1-8c41e711b837@tana.it> you write:
>In the pre-DMARC era, we've been mainly using just From:.  Sender: is used by 
>Outlook to display "on behalf of" catchphrase, presumably in an attempt to 
>support the historic Sender-Id protocol. 

Sorry, no. That is completely wrong. The Sender field has been part of
e-mail since RFC 724 in 1977. The now-dead Sender-ID didn't come along
until the 2000s. Outlook's annoying "on behalf of" at least matches the
intention of the Sender field.

This might be a good time to read up on mail history rather than guessing.

R's,
John