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

Jim Fenton <fenton@bluepopcorn.net> Tue, 05 January 2021 18:50 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 5FEBC3A1147 for <dmarc@ietfa.amsl.com>; Tue, 5 Jan 2021 10:50:41 -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 S2wfYDDAaVc8 for <dmarc@ietfa.amsl.com>; Tue, 5 Jan 2021 10:50:39 -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 C8C8C3A1158 for <dmarc@ietf.org>; Tue, 5 Jan 2021 10:50:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To: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=sCovOmI0GhNzj/Rx+j211HU5TbwmGqCAibxlq7iXK1c=; b=XA2BgcpnvGp6xQ6JBqCZuBL3zg 7O/b5/SyrSZ+A8HgYyAqEd9U0Xx3qY7toJeq3dlW+doBamuUY+u+1qxckh6upK59cAKIL4Ah8Ja2U XPfML99pCe7sRWRVn66EaLz1yNhQoFMBSS1xJKUE9x9js1enJUbJryjotYebMbCY8TMI=;
Received: from [2601:647:4400:1261:108d:ac48:81ff:6e96] (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 1kwrPj-0005d8-0B; Tue, 05 Jan 2021 10:50:39 -0800
From: Jim Fenton <fenton@bluepopcorn.net>
To: Paypal security confirm your password now <johnl@taugh.com>
Cc: dmarc@ietf.org
Date: Tue, 05 Jan 2021 10:50:38 -0800
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <A2966FEB-45C6-46E1-8D7C-E811C785666A@bluepopcorn.net>
In-Reply-To: <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com>
References: <20210104174623.2545154CFF9F@ary.qy> <FD45F9FC-46B0-40A9-ADC6-DDD7650D62F2@bluepopcorn.net> <ae77d9f-6f63-16ca-903a-7cb463a7b58d@taugh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"; markup="markdown"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/eaAndLrLxxuV0jIkRJBruG2XRdk>
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, 05 Jan 2021 18:50:41 -0000


On 5 Jan 2021, at 10:17, Paypal security confirm your password now 
wrote:

>>> 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.
>>
>> Because recipients often can’t see (or don’t pay attention to) 
>> the domain name and the reputation system you postulate doesn’t 
>> exist. OTOH, getting alignment avoids a restrictive policy that might 
>> be associated with the original domain.
>
> I think you're saying that I can always evade DMARC problems by 
> putting an address I control on the From line and nobody will notice.  
> That would mean that DMARC is useless.
>
> If that's not what you're saying, could you clarify?

I used the word “often” and indeed some people will notice as I did. 
But I recall we beat this issue to death a few months ago, although 
I’m not sure what WG consensus on that was, if any.

It looks like we’ve strayed pretty far from the subject line (failure 
reports) though.

-Jim