IETF Logo Mail Archive

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

Jim Fenton <fenton@bluepopcorn.net> Wed, 30 December 2020 23:22 UTC

Return-Path: <fenton@bluepopcorn.net>
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 3731D3A0B17 for <dmarc@ietfa.amsl.com>; Wed, 30 Dec 2020 15:22:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
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 wKlTEHLo3zW0 for <dmarc@ietfa.amsl.com>; Wed, 30 Dec 2020 15:22:54 -0800 (PST)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 0D9C13A0B16 for <dmarc@ietf.org>; Wed, 30 Dec 2020 15:22:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=9jKrSOQ/MPkdl8Dd4+VXeqiwvQPt56YiqA0FxmIpwdY=; b=eF0r24jC8jDmkpXiLd8W8dn82 JKNS5wguqlqVv3ELskdWb8A+1a9m0pWQEInvs4hTpUbYc4ptghcIH0tETopN+dO2DiCDfyco4FBUH 8uLG4PsDYm6DRn9Z2DdiCSBLHSCkA+zEbDhbU4tE5dONprEJ8NZ+nLUljfmYvTLyRosVo=;
Received: from [2601:647:4400:1261:a85c:7e61:f695:5964] (helo=[10.10.20.144]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1kuknr-0001f0-8v; Wed, 30 Dec 2020 15:22:51 -0800
From: Jim Fenton <fenton@bluepopcorn.net>
To: John Levine <johnl@taugh.com>
Cc: dmarc@ietf.org, mike@mtcc.com
Date: Wed, 30 Dec 2020 15:22:49 -0800
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <1429C59C-5DBC-4B35-B6D6-2A2D78C783F4@bluepopcorn.net>
In-Reply-To: <20201229205922.BD91635185C5@ary.qy>
References: <20201229205922.BD91635185C5@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/BjU_c5xOUyvv218dcI_OZeLOZCY>
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: Wed, 30 Dec 2020 23:22:55 -0000

On 29 Dec 2020, at 12:59, John Levine wrote:

> 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.

But these Girl Scout troops are going to publish a DMARC policy despite 
their lack of expertise?

v2.23.0 | Report a Bug | By Email