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 20:10 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 316643A093D for <dmarc@ietfa.amsl.com>; Tue, 29 Dec 2020 12:10:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level:
X-Spam-Status: No, score=-1.849 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, RCVD_IN_DNSWL_BLOCKED=0.001, 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=BRoUoF5Y; dkim=pass (2048-bit key) header.d=taugh.com header.b=Go6iT7lP
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 D-OFu995f1Gq for <dmarc@ietfa.amsl.com>; Tue, 29 Dec 2020 12:10:56 -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 A91D23A0934 for <dmarc@ietf.org>; Tue, 29 Dec 2020 12:10:56 -0800 (PST)
Received: (qmail 81872 invoked from network); 29 Dec 2020 20:10:54 -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=13fce.5feb8d4e.k2012; bh=C/m5JAcvq4gjqtTwg8F20N4UNe9mXgUqpzH9I8PE/ig=; b=BRoUoF5Ybh/omepwyBgzKn9c5oHaCiRvKnQudUUxG6Lus+6jb5mQXF31SogZC/J8hyh+3xLps7B7uzILOUhDGEV2z1hN2jHWvXqxfnlRM/nGmSl1s/TmZI0M3qebp5ZxPmLLsfiCl2Es0hN/vtKCLXw6N7zVyxHQ42rcxKgD8x9XOopdybjKome32HU5Pv/CFNuF05UJbJmeLX6zQk2nWef0PMunnsGNpIjhdqUS6BZnbvTEnHsgpOXnjwH8nwH+eBNu2EdpVgc65M+0g/f5O60r/rLBhEJNj0WDlvMoK6Rhp/vUmJjj2hcwmK1A24xbaFHIK6TpVGhaoORy/QFCGg==
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=13fce.5feb8d4e.k2012; bh=C/m5JAcvq4gjqtTwg8F20N4UNe9mXgUqpzH9I8PE/ig=; b=Go6iT7lPEbk5lhrrjSAX2ssi4mtjM/QijgE6ZgxyF+/2uzbzgIezCI9kR/wrRgZkwFEdkDXy7/6t7Xw686wYmMlSBHMr+ugbKi01YFM4VouIWZ2d97SbYn/DUYaFyUsELOc0ObskDpSxldk2GjA3S1sfdqQFrbT9TEBYGod+orX17LXnIzFL43QaxTinYtsqg3Uuo1i4ekWQgd0pBN/QCLM/0fgBtzLbMN+gMflrAQzDZcq/owOMdD7Msf2zO7rpB2dJ7QqydQmB39mSW2NtaYQcqxFXfgYPP1mgaFy1SdTySsd2rZy+xoh0vmVAe0OKiwY/ZnJlU+KV4GxFBds3lg==
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 20:10:53 -0000
Received: by ary.qy (Postfix, from userid 501) id 5A7EC34FD94A; Tue, 29 Dec 2020 15:10:52 -0500 (EST)
Date: Tue, 29 Dec 2020 15:10:52 -0500
Message-Id: <20201229201053.5A7EC34FD94A@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: mike@mtcc.com
In-Reply-To: <5d0793ae-de65-cd1d-32ef-c909202a0eb6@mtcc.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/sELnS16jVGKfhiZ8cLq5aZ0eEEE>
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 20:10:58 -0000

In article <5d0793ae-de65-cd1d-32ef-c909202a0eb6@mtcc.com> you write:
>
>On 12/29/20 10:59 AM, John Levine wrote:
>>
>> Don't forget
>>
>>   o Normal forwarding of SPF validated mail
>>   o Authorized third party senders with no access to DKIM keys
>>
>If by "authorized" you mean authorized by the originating domain, I don' 
>t have a lot of sympathy since they can delegate them a selector and 
>update their DNS. Not doing so is just lazy.

A lot of tiny non-profits like Girl Scout troops use email addresses
at webmail providers and send their announcements through ESPs like
Constant Contact and Mailchimp.  This is yet another situation where
DMARC can't describe an entirely normal mail setup.

Constant Contact apparently got Yahoo to give them a signing key,
at least temporarily, but that doesn't scale.

R's,
John

v2.23.0 | Report a Bug | By Email