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

Alessandro Vesely <vesely@tana.it> Thu, 31 December 2020 18:06 UTC

Return-Path: <vesely@tana.it>
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 2F0A23A0E13 for <dmarc@ietfa.amsl.com>; Thu, 31 Dec 2020 10:06:40 -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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
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 9XXcKBWT1sqY for <dmarc@ietfa.amsl.com>; Thu, 31 Dec 2020 10:06:39 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (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 E4B963A0E12 for <dmarc@ietf.org>; Thu, 31 Dec 2020 10:06:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1609437995; bh=h68bBa5FAg6tT3PBtsm10Z2kFYmFSQJMdE/L9be1r4Q=; l=485; h=To:References:From:Date:In-Reply-To; b=AjpKH9+0RxgiZm86Z1Mpfb9lMDjCYNUmQxtpmbgpKcZSANkHTiNd3MjPtPh0N8CBj bTFDoZ1xftDY5TmH0H6/YpP1cuaej1CnLOqMpTDhaj+Uwsyg7MfIbhwsjexBQgsg40 sqAC0XdJAxFUEGU+K4fj93eST2RHNr97yUmCxBq5Q5WzIO/C+4Byg+KCpddNx
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC053.000000005FEE132B.0000298E; Thu, 31 Dec 2020 19:06:35 +0100
To: John R Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20201231160030.20AFB3EE7AD7@ary.qy> <4bd444a4-0c34-467a-cfcb-a8f7c14b723d@tana.it> <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <3999b617-b0e7-7341-93df-4a2ccea134e4@tana.it>
Date: Thu, 31 Dec 2020 19:06:35 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <b030d1f-44d4-4330-eb17-c930eb968be2@taugh.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/laEctVkvndIdl2U7oXmhZsz4sO8>
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: Thu, 31 Dec 2020 18:06:40 -0000

On Thu 31/Dec/2020 18:51:10 +0100 John R Levine wrote:
>>> The main effect is that the mail they'd been sending from their ESP
>>> with their Yahoo address on the From: line used to work, and now falls
>>> on the floor or worse.
>>
>> Why can't the ESPs do From: rewriting?
> 
> To what?  The Yahoo address is the only address the scout troop has?


Copy that to Reply-To: and write a mangled From: that looks troopy but passes 
DMARC.  Just like MLMs do.


Best
Ale
--