IETF Logo Mail Archive

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

John Levine <johnl@taugh.com> Tue, 29 December 2020 18:59 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 0AF4A3A07F7 for <dmarc@ietfa.amsl.com>; Tue, 29 Dec 2020 10:59:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 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.25, 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=ubTOC/1H; dkim=pass (2048-bit key) header.d=taugh.com header.b=Tv/tN4zR
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 uyj4paQyGULB for <dmarc@ietfa.amsl.com>; Tue, 29 Dec 2020 10:59:11 -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 630413A07F4 for <dmarc@ietf.org>; Tue, 29 Dec 2020 10:59:11 -0800 (PST)
Received: (qmail 60923 invoked from network); 29 Dec 2020 18:59:10 -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=edf8.5feb7c7e.k2012; bh=Wpf6fdpKdidijre1z/UZq7HVS/QIoParjtug0i1hd0w=; b=ubTOC/1Hl8vSLIY2+gY1CwAeoa00K13ocpuKfVpWCjl+HbRE2WuSKsCnjNxAjX9Lq7pHB84iodF2LP9vCynnDrKe2VAU/wFWpuoeBL1k9+f3x+8f2SIxKmz6pQ+CAbPhkT4e8Tm6KdgFrP1C0ivncJdQXA4kN3u+1L7N7fBd1Lw9gAaN/rkC3Wi0gcVXm+EYoTIApftTKyWdY6gokbm5Jx8Hy1z3SHPzGawsJwcXSXRNk2lr4FusiC1u9yswKh0R+4LONE2ozyZahtfiK8iI8IYPgBF4ssPR7Wa9doOvNi4zLtN45HSnTP8Qx0CNcVq8zLRickFrvTm75Iu0j20oGQ==
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=edf8.5feb7c7e.k2012; bh=Wpf6fdpKdidijre1z/UZq7HVS/QIoParjtug0i1hd0w=; b=Tv/tN4zR/SilH8wRKUFGDKKTGE4ybTd3TaQcd45sJqT+uBh4oMqq45fe/eh6t1HPJjTRn9FoLeSJhK78qQvM+4lUCB2o8Gdd+x3S1yl4AiA+4uAuwOVYm1Bhzq2k6f5Fw/A27XdCo5uenqHou48hKksX7qOMF8v76m3HKcZw4o3oDiQymt6Hz6NyZbhHzdzA+WZcl6qC3JV8MS68rdtC+rlUGBgErzGe2ToHKiyDhI84KxWqSJpFO7qiYCiRAkFz/3HKe61IutkM+F88onhfV63Zbcor6FcjSpbzTJV6IQUpYP6k4k21rtXgteBCQgNiPSEkjIHCD2sjPidWzQHMgg==
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; 29 Dec 2020 18:59:09 -0000
Received: by ary.qy (Postfix, from userid 501) id 856AD34F063E; Tue, 29 Dec 2020 13:59:09 -0500 (EST)
Date: Tue, 29 Dec 2020 13:59:09 -0500
Message-Id: <20201229185909.856AD34F063E@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: ned+dmarc@mrochek.com
In-Reply-To: <01RTQRKLD8QK004QVR@mauve.mrochek.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/hkd3M3YxhcChlNohBdK82Gc9XZY>
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: Tue, 29 Dec 2020 18:59:13 -0000

In article <01RTQRKLD8QK004QVR@mauve.mrochek.com> you write:
>I think a list of possible failure causes would be nice to have, because
>a lot of people seem to think that DMARC is a completely reliable mechanism.
>
>I'm not entirely convinced this document is the place for it, but OTOH
>I'm not convinced it isn't.

Sounds like a separate WCP document.  I agree it could be nice to have something
to point to when people insist that it's my fault that their DMARC rules don't
match the way my mail system works.

>It also strikes me as more of an exercise in enumeration of possibilities than
>an actual analysis.
>
>Let's see. We have:
>
>  o Illegitimate mail
>  o Message changed in transit, invalidating DKIM signature
>  o Incorrect DKIM signing
>  o Incorrect SPF setup
>  o Unintentional domain misalignment
>  o Improper assertion of DMARC policy

Don't forget

 o Normal forwarding of SPF validated mail
 o Authorized third party senders with no access to DKIM keys

Could be an interesting document.

R's,
John

v2.23.0 | Report a Bug | By Email