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

John Levine <johnl@taugh.com> Tue, 29 December 2020 20: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 656DE3A0A29 for <dmarc@ietfa.amsl.com>; Tue, 29 Dec 2020 12:59:26 -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=ewzkQ34I; dkim=pass (2048-bit key) header.d=taugh.com header.b=PHJe5g0N
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 BIr-zcNbGgcP for <dmarc@ietfa.amsl.com>; Tue, 29 Dec 2020 12:59: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 AE7173A0A22 for <dmarc@ietf.org>; Tue, 29 Dec 2020 12:59:24 -0800 (PST)
Received: (qmail 94126 invoked from network); 29 Dec 2020 20:59:23 -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=16fac.5feb98ab.k2012; bh=E5P3QjT6PC+ieSZ+ePmb/tXEGj3rMZE7PynO8fZA8Rs=; b=ewzkQ34ImvRKNF0iAMYnEk2jx1ORu4G9myqWYUb//832YRroiAodGNPKO5mjYhq+jnQFKaVHXea2i4ZL/xXPf298yWKPeIsxvgKvdcTX7PfRxuMWeNvypoYhDkUF7aAWQ10MkyPL6jrYTXopk4i4pJL5NeiLlC2c19hS8UAffkftVU0pKdKhtRFaHcC/imRmvBh5FT3PHe/LoY65l4M6jMD9M2v5BrOVAdX4s/qu2fGRr004fIc3dlksfrzH8lPlbzACI3+M9kC40GtdUzPzRycp9EZVHh775ksU6+t/PHsgOoPJrShrsGGDWUH4RHz2r7+U8RfyoqVE0JVEf7L1oQ==
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=16fac.5feb98ab.k2012; bh=E5P3QjT6PC+ieSZ+ePmb/tXEGj3rMZE7PynO8fZA8Rs=; b=PHJe5g0NG8SK5ylj2st/pqHPOO/B4eMifLtoTW8ndeGw0zWRyoK/C603eDcVxQ5lKy8Gx+mEH7HXxVQmZL7HBMRKKjX3DyVVJyKb+oJX1UMjd0XMWSMVJUmaSKYfDCDt8DNbr4EkN61OkXck4K9aOzeSlfd3y7p6puQN4uD1vBDOvpqVSgi+6kAbeCCwJpcKisFoDSH5C79P4Mw/5+zBMqZSo4m1sq9JJzEeg2AkJWUjl2UDt9DSWrM26X8gNqo+dROwOlwNMJ8AQsP9ozlOtmFPO24me7eXvpjVPZxOqUmZjoK8Nvo+ZImdz7dO8saqyUtoy7OamaZo4K8j7nKEgg==
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:59:23 -0000
Received: by ary.qy (Postfix, from userid 501) id BD91635185C5; Tue, 29 Dec 2020 15:59:22 -0500 (EST)
Date: Tue, 29 Dec 2020 15:59:22 -0500
Message-Id: <20201229205922.BD91635185C5@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: mike@mtcc.com
In-Reply-To: <14d833ce-0ae0-f818-fd4f-95769266a8e0@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/AvAN-W688k0jQ2TGcblPTNTMXOU>
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:59:26 -0000

In article <14d833ce-0ae0-f818-fd4f-95769266a8e0@mtcc.com> you write:
>
>On 12/29/20 12:10 PM, John Levine wrote:
>> 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.
>
>What gmail does for gsuite is generates (or not, who knows) a key and 
>gives you the selector to add to your dns. I don't see why that doesn't 
>scale for all situations.

To point out the obvious, because they use a single address at
yahoo.com or gmail.com or hotmail.com, not a private domain. These are
tiny organizations that don't have a lot of computer expertise nor a
lot of need for it.