IETF Logo Mail Archive

Re: [dmarc-ietf] non-mailing list use case for differing header domains

John Levine <johnl@taugh.com> Tue, 28 July 2020 17:37 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 7319B3A0A53 for <dmarc@ietfa.amsl.com>; Tue, 28 Jul 2020 10:37:19 -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=HI9WVSeZ; dkim=pass (1536-bit key) header.d=taugh.com header.b=F2BgghYH
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 hCDUAsQSxYpv for <dmarc@ietfa.amsl.com>; Tue, 28 Jul 2020 10:37:18 -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 E86FB3A0A49 for <dmarc@ietf.org>; Tue, 28 Jul 2020 10:37:17 -0700 (PDT)
Received: (qmail 79491 invoked from network); 28 Jul 2020 17:37:16 -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=13680.5f20624c.k2007; bh=lVH+uu98EjCJkVhzWKhe0LhYVvO74AeBpjXfmq2bBOk=; b=HI9WVSeZVc6EgAgDVoqtxnzZvRg/akOCDrrHu6W4VHzj1iINbSKzxs++uI+0ry6f5u9DwF0WOA8N2MW0a59E1LCeMtPlINzbk0utlKq5ZS2jI5km6MaXOIExdbWi/kyqwMwIlDH7XTxgFXVIcObljXca73R89FuX+vzUsV0E1GEDmSKS80+Sp+9jy0ayO5JaEWIE616VImn61qs/PdunwRA10Iu8n9EOpzdLl78vG1Xblfq/oZmTGt4j9q7ouXIr
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=13680.5f20624c.k2007; bh=lVH+uu98EjCJkVhzWKhe0LhYVvO74AeBpjXfmq2bBOk=; b=F2BgghYHI+vZI17dcI2T4uSF0/9yisSyR9GnFKbE65AwuYx8ZON02NzB4jT9ja3blYQwozvOjyLSe0ZNaR9U9gSc/dcfI14CQIkMM4sP3e7kv/TbcKXdcZ5KynAZEGcap5Vpnm0p4F7CTj6aAhGGVUsliAafHiycgkNwPEzK/FfpnvkNL7xnmy7naYwAntglHO+gLRrJtrAiujfiJc04P/aCx2ZM50k9rKs1M9UOL6ElgslLFYWb5eh5J0bJrTdV
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:37:16 -0000
Received: by ary.qy (Postfix, from userid 501) id 068CB1D9840C; Tue, 28 Jul 2020 13:37:16 -0400 (EDT)
Date: Tue, 28 Jul 2020 13:37:16 -0400
Message-Id: <20200728173716.068CB1D9840C@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: atyrsalvia@agari.com
In-Reply-To: <BY5PR13MB29998094418C8A6C25902569D7730@BY5PR13MB2999.namprd13.prod.outlook.com>
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/ie-FoHzGttnisdGFkiKCE-pmWQI>
Subject: Re: [dmarc-ietf] non-mailing list use case for differing header domains
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:37:20 -0000

In article <BY5PR13MB29998094418C8A6C25902569D7730@BY5PR13MB2999.namprd13.prod.outlook.com> you write:
>To put it another way:
>
>  *   assistant@firstbrand.com is organizing a meeting for executive@secondbrand.com
>  *   assistant@firstbrand.com sends out a calendar invite from their own messaging client, using
>executive@secondbrand.com in the From: field
>  *   The resulting message uses executive@secondbrand.com in the friendly From: field, but firstbrand.com in the
>SMTP MAIL FROM domain, so the headers are no longer aligned for SPF.
>  *   Both firstbrand.com and secondbrand.com are set to DMARC p=reject.
>  *   Messages like this are then rejected by receivers that validate DMARC results.

This sounds like an excellent use case for Dave's draft-crocker-dmarc-sender proposal.

The canonical example of different From and Sender is exactly this:
Sender is an assistant working for and sending mail for From.

R's,
John

v2.23.0 | Report a Bug | By Email