Re: [dmarc-ietf] Forensic report loops are a problem

Alessandro Vesely <vesely@tana.it> Mon, 01 February 2021 18:08 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 49B573A1380 for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 10:08:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 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.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 LvcIzz1jBdvA for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 10:08:27 -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 0B65C3A137E for <dmarc@ietf.org>; Mon, 1 Feb 2021 10:08:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612202905; bh=LRtWExRJOV7JQjGGDUCbO40A9g4Te0LDbd4iY5ZTcS4=; l=344; h=To:References:From:Date:In-Reply-To; b=DD+ebXgf6BSHoKMKn05pjkNupareIekJIMDMAr97mYSILxiN/66eRHIPY0KxniCgT CDJcYvFEuWdhQqY9/gCDCm7Fnxgu2i//8jcCkCihr4glwJzI5gUroLcXzEFR2gFdK6 m0Qf4QqbIJopPZNfGpo9sWtNtFP/yjQKZyB8KBQNSwJQHiuRkPWnnilS0BQf5
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 00000000005DC07E.0000000060184399.000043CE; Mon, 01 Feb 2021 19:08:25 +0100
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> <20210127203714.007C86CDB9CA@ary.qy> <CAL0qLwbN+HkGfvw79rPPvqL6jWWAsUtWY9X1gW=vAvoeQS8RHg@mail.gmail.com> <b7ea6cb8-ce79-7df7-c521-544358c1866e@crash.com> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <379e4493-1287-9dd5-5c8f-ae5adf949cbd@tana.it>
Date: Mon, 1 Feb 2021 19:08:24 +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: <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.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/alorLoU_zlOb42tIdSNG9MYe7Yw>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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, 01 Feb 2021 18:08:28 -0000

On Mon 01/Feb/2021 17:38:07 +0100 Dave Crocker wrote:
> 
> Consider the challenges to ensuring a DMARC pass.  That's a pretty high barrier 
> to entry against generating reports.


Well, if a mail site is unable to get a DMARC pass, they have more urgent 
problems to solve than setting up aggregate report generation.


Best
Ale
--