Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports

John Levine <johnl@taugh.com> Mon, 04 January 2021 17:46 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 F36A93A0EBE for <dmarc@ietfa.amsl.com>; Mon, 4 Jan 2021 09:46:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.048
X-Spam-Level:
X-Spam-Status: No, score=0.048 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=NQRvrFUw; dkim=pass (2048-bit key) header.d=taugh.com header.b=oyYPbRie
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 mmP5qFL6Q271 for <dmarc@ietfa.amsl.com>; Mon, 4 Jan 2021 09:46:25 -0800 (PST)
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 2628E3A0EBC for <dmarc@ietf.org>; Mon, 4 Jan 2021 09:46:24 -0800 (PST)
Received: (qmail 63079 invoked from network); 4 Jan 2021 17:46:24 -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:cleverness; s=f665.5ff35470.k2101; bh=d+HVFRiZ+W6v4RLUkSwNkE2+BRpWQyL3wkyghh+Nu/E=; b=NQRvrFUwDkZn0vOkks7v/TNUmzhF8TrWUvgqH9P6pyypObxUEOUugEJ810K1ZFok6Gg1QKYJoUD3o+YeR+uN/NzU61qmvsguRHoCZtGpYa+o5twKp07v1Q0n0ozfhCPcEEjtq/XW/k4mdMTmyz8lhOq40QCEIxpJzREEjnyIwF449XMuuPWevyNgKamC+aB9XWzpx+quvarr6XwZx0GapDxY3HTecSlrrNGJN4qkktaY9N6HIORJMHafINaZ7cgzXgco508o2GFOgR0De4Fy6LImk1iNAGQW/cxI+HaSFPXvTIFxfPtBLac5G6f5rwaiXpqkXbyk1TRQ5qo6O/pQOA==
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:cleverness; s=f665.5ff35470.k2101; bh=d+HVFRiZ+W6v4RLUkSwNkE2+BRpWQyL3wkyghh+Nu/E=; b=oyYPbRieS3zusGRqJ66gb/gFt7ld4Y7bIhTEmTSzFj3hyYanLD6ajsyANFHb9oSSkDa8yseYKYFQ+QJrTEM9k8Eb2Hjw0/jZfcUPqU7MJJrG6eFBKxrd724C1SLnI4HXVNsq7Sx5vfgrxM1zaPVo7LXMGvjn7UDvuDYjJbMlV5UVFaIrJPZzgbdsPCwmqFQ+fVw3tbBFBNgkDd6e1otuSE6WRJFfbwL4ocbXq+X1UA40LbCqowqkkXjCMIfBho77+KlaQCyJwttUV8Qe85sF8PRHHi92vnwMtV97QVUBP+3B9aT77pB1dv0inxJubvYWBF9/C53U67fMJBnw6Q8p7w==
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; 04 Jan 2021 17:46:23 -0000
Received: by ary.qy (Postfix, from userid 501) id 2545154CFF9F; Mon, 4 Jan 2021 12:46:22 -0500 (EST)
Date: Mon, 04 Jan 2021 12:46:22 -0500
Message-Id: <20210104174623.2545154CFF9F@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: laura@wordtothewise.com
In-Reply-To: <123E18E2-71AB-4946-B886-A12A735AA1AC@wordtothewise.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/DpcTy6Bg8LLOd3TxaYlsDa9v01Y>
Subject: Re: [dmarc-ietf] Ticket #55 - Clarify legal and privacy implications of failure reports
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: Mon, 04 Jan 2021 17:46:27 -0000

In article <123E18E2-71AB-4946-B886-A12A735AA1AC@wordtothewise.com> you write:
>There is absolutely nothing stopping a phisher from taking advantage of this. In fact, phishers currently do send DMARC verified email where the
>domain in the 5322.from is unrelated to the links in the message or to the domain being phished. 
>
>This seems to me to be a step along the path of making DMARC irrelevant by teaching recipients that mail with a 5322.from address they don’t
>recognize is legitimate email. 

We went through this same argument with DKIM 15 years ago, explaining
over and over to people who imagined that DKIM was a magic whitelist
bullet that a DKIM signature by itself tells you nothing. It's only
useful if you know something, good or bad, about the domain.

Similarly, DMARC alignment tells you nothing unless you also have a
reputation for the domain. I have trouble imagining why anyone would
think it's a good idea to get alignment by using third party domains
that recipients don't know.

R's,
John