Re: [dmarc-ietf] DMARC alignment conflicts with RFC 5322 on the use of the From and Sender header fields

John Levine <johnl@taugh.com> Thu, 04 June 2020 16:32 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 E53993A0B20 for <dmarc@ietfa.amsl.com>; Thu, 4 Jun 2020 09:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.451
X-Spam-Level:
X-Spam-Status: No, score=-1.451 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1536-bit key) reason="fail (message has been altered)" header.d=iecc.com header.b=C9aEAB21; dkim=fail (1536-bit key) reason="fail (message has been altered)" header.d=taugh.com header.b=TvyNaizF
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 MUQskR_awboq for <dmarc@ietfa.amsl.com>; Thu, 4 Jun 2020 09:32:31 -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 2A3B33A0B23 for <dmarc@ietf.org>; Thu, 4 Jun 2020 09:32:30 -0700 (PDT)
Received: (qmail 49377 invoked by uid 100); 4 Jun 2020 16:32:27 -0000
Date: Thu, 04 Jun 2020 16:32:26 -0000
Message-ID: <rbb7mq$1e3n$1@gal.iecc.com>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:references:in-reply-to:cleverness; s=c0d6.5ed9221b.k2006; i=news@user.iecc.com; bh=fgjaAgJbGmvvHpp0rCS7U5rqKkhDw4FX6ppQW1NEPvY=; b=C9aEAB21IHXj74z8ss59ZGROj9jtuwxbs5eA+/FVb5EZhtuuuz34VeAbwZp71PQMOf6Lz72bYjly6lvO8u7+yRxdEzyiHemXnV2YtBvuluU/1+30wMzpQqB/TZC7wES9ocYtAWMzormgIlc3dCjBKweFyJzflTPMiarGoYRU4S9KDxTtJCMS1vyWTtisFRLZIyJXp6V3+QiUQHho5Qv1F9WoIxblgv/6Y4ZoApJaBG/sbYRyDHpXNC2HxKbjtC24
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:references:in-reply-to:cleverness; s=c0d6.5ed9221b.k2006; olt=news@user.iecc.com; bh=fgjaAgJbGmvvHpp0rCS7U5rqKkhDw4FX6ppQW1NEPvY=; b=TvyNaizFv02IFBwAnO6JUDr+VfDM19UCdmd/MRBar0E6sZ0JhdPptN0lcaNLohcrDCkw4gVHOw01zpttceAXpr8rIoVfRQmwgS2UWjN47bxElqdXFBGhWJCE+mQ8HBM2WKQzPDxBeSMGOQsNrYppAFXBtIYGebGFZSoTZ3PWC0meXTFn2psch3FRtDFNPp1yHxubokElj42LYLjf+19aRoLCFv0OfN3rsxqK2UTFqKLB0kXpa5TcqqJHUR7E5P/3
Organization: Taughannock Networks
References: <DM5PR0601MB367115AD49513EAF3953716CF68B0@DM5PR0601MB3671.namprd06.prod.outlook.com> <1f04f4fd-5c92-b61d-3ca1-e6ea954e33f7@gmail.com> <b23c91d7-d1b6-6a90-6f59-57178b0fa826@tana.it> <652580c1-5f8b-4d11-af25-d968b277c2b5@www.fastmail.com>
In-Reply-To: <DM5PR0601MB367115AD49513EAF3953716CF68B0@DM5PR0601MB3671.namprd06.prod.outlook.com> <1f04f4fd-5c92-b61d-3ca1-e6ea954e33f7@gmail.com> <b23c91d7-d1b6-6a90-6f59-57178b0fa826@tana.it> <652580c1-5f8b-4d11-af25-d968b277c2b5@www.fastmail.com>
Cleverness: some
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: johnl@iecc.com (John Levine)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/M6hIBGpBsdFhmIKoKfIo4xY7iB4>
Subject: Re: [dmarc-ietf] DMARC alignment conflicts with RFC 5322 on the use of the From and Sender header fields
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: Thu, 04 Jun 2020 16:32:33 -0000

In article <652580c1-5f8b-4d11-af25-d968b277c2b5@www.fastmail.com>,
Stan Kalisch  <stan@glyphein.mailforce.net> wrote:
>> That depends on who creates the Author: field.  I'd imagine it can be created
>> on rewriting From:.  If it exists already at that time, one can still check (by
>> ARC?) if it was signed, and, in case, sign it in turn.
>
>I, too, was wondering whether ARC was really the only practical way to attempt this, assuming you
>don't think it deviates enough from ARC's purpose.

It took me a while to understand why ARC works the way it does but now
that I do, I don't think anything simpler would do.

In particular, anything that lets you say "I'm a mailing list" is out
since spammers can do that too. Also, real mailing lists tend to have
lousy spam filtering and leak a lot of spam, so you can't just
whitelist everything from even real lists.

-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly