Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help

Alessandro Vesely <vesely@tana.it> Mon, 25 January 2021 20:39 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 2D9BC3A18E4 for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level:
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[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.01, RCVD_IN_MSPIKE_WL=-0.01, 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 oWIxTuScME6c for <dmarc@ietfa.amsl.com>; Mon, 25 Jan 2021 12:39:09 -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 DBF183A18E6 for <dmarc@ietf.org>; Mon, 25 Jan 2021 12:39:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611607146; bh=bJfHW4aIsI0IQJcKUx4hVrXyg5f9XigWc0qq/60Cocc=; l=700; h=To:References:From:Date:In-Reply-To; b=Cgs22kMa2jlAJKY2fagcqLuB1q3rU2X7a0+eJp6GN4qhqAkiGHLnc3SmiG6WKAl/F RKel55y5oBAm3B8+pvyZ8sB0One5mJUPKRvnW+zf1M7wAlrDq9KbdmxpZKlPJjeFec 5f4NAsOYSO/zTE6HL+S7Vqw97/tKCwHcg25sdr9NWYhga2I3XjZ7GzCycjVLA
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.00000000600F2C6A.0000132E; Mon, 25 Jan 2021 21:39:06 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org, dougfoster.emailstandards@gmail.com
References: <20210125195231.E0DE16C13E26@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <62e65ae9-f7d3-af7c-94f1-63bf07bd38cc@tana.it>
Date: Mon, 25 Jan 2021 21:39:05 +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: <20210125195231.E0DE16C13E26@ary.qy>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/GaoToSC0gcbKtjYn2piKk4GOVag>
Subject: Re: [dmarc-ietf] Tickets 98 and 99 -- fake reports are not a problem and if they were authentication would not help
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: Mon, 25 Jan 2021 20:39:11 -0000

On Mon 25/Jan/2021 20:52:31 +0100 John Levine wrote:
> In article <CAH48ZfwejX1PHO7x1bjJTYyehXZWMuq3jrHFJzAHWfy1jQ+NQg@mail.gmail.com> you write:
>>
>>DMARC alignment on the report seems of limited value unless it is aligned
>>to the domain being reported. ...
> 
> [...]
> 
> For at least the third time, there is no "domain being reported". When
> I get reports from Google or any other multi-tenant mail provider,
> they do not say to which of their gazillion hosted domains the mail
> was sent. That is not a bug, and it's been like that for a decade.


Yet, an unauthenticated report from Google would prick up your ears.

DMARC authentication is a good thing.


Best
Ale
--