Re: [dmarc-ietf] DMARC'ed reports, was Forensic report loops are a problem

Dave Crocker <dcrocker@gmail.com> Tue, 02 February 2021 01:42 UTC

Return-Path: <dcrocker@gmail.com>
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 549463A165F for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 17:42:30 -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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, 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 (2048-bit key) header.d=gmail.com
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 nMjx60bekrXu for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 17:42:29 -0800 (PST)
Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17DA43A1654 for <dmarc@ietf.org>; Mon, 1 Feb 2021 17:42:29 -0800 (PST)
Received: by mail-ot1-x32c.google.com with SMTP id h14so18371881otr.4 for <dmarc@ietf.org>; Mon, 01 Feb 2021 17:42:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=/vD7WoQqjrSg5ZVABfjazd/6amj1T8V1e4HTEE26KYU=; b=kr7ATpz96diwnezt4HZmkFT4q8MdjXtY2s5HoJe3nWN3x7CUsTa2YibRCz6ZMaEQj5 fFIfnPuyixR+WoU0oM1JnCl7YXcGSTABsCyDei2cme308ie/pE51ELq4gC+UKjc/HwnX gHvChjUu20ZJv6LU0Yfjbr1MlfeY9x3p9udZCtT6PfEdq/94o3hQ2GOxZQYizZkIWo8v ynldwqrLDa/6X1i5/io+phwGRkAzC68wkQSfXIJlq6ai9TLU/bHiHg3/ulNXEUNYgWLY Su0lsHFJjO3dTmgjFcAB0+Kic3UnF/lhzgzohShZL4JrKenEClstx/+1LqY+aINP3wuc SnLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=/vD7WoQqjrSg5ZVABfjazd/6amj1T8V1e4HTEE26KYU=; b=rGbv7lp1NnoCSvoIQ4k1RCYwux5xaxpEuRgH1eOsGm25KUsKCcXFrFxbG+wKM61/P4 ciaAcVjg9TPWDa6TmhrMhUDFpNeRKg1vjEhOqdpxxpQK8/qcs0+0+ztoH+WHFYeCxZnZ NFniV3ZjxJZrSOOzP0R9KPzGZU2Z2LPSz/+7TRYN3qQsBO2rGNJ0xgo0phLC6yG1d9VK QAnTplg66n7ubq6HPCB1cJlqmNcGouJRqaLddvS89okGuF82kCQJ5bqhY6tVw6hgVC/v Tbx4aeFRXDkHuQb2rVyERcb+h4o7EzuyiTAAB5UsCPisFVHivsXTnuiNLKM9a3oEX/4e MPaA==
X-Gm-Message-State: AOAM531IEBhfFeBZirHXvzv5vURsXP159stvlLGGTR7rU53yQpJsW5qg beyGcQQ64/SIywaj6rMU4Klt/52DuGo3SQ==
X-Google-Smtp-Source: ABdhPJz9eN11ov/1Qf2z5mI0j9t+vxY0RR1Rlsf/tvrbLy+YUhmsST8ffxY1yB7p1PFRSL/fbWCJiw==
X-Received: by 2002:a05:6830:1dc8:: with SMTP id a8mr13856852otj.26.1612230148351; Mon, 01 Feb 2021 17:42:28 -0800 (PST)
Received: from [192.168.0.109] (108-226-162-63.lightspeed.sntcca.sbcglobal.net. [108.226.162.63]) by smtp.gmail.com with ESMTPSA id 33sm4255319ota.69.2021.02.01.17.42.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 17:42:27 -0800 (PST)
To: John R Levine <johnl@taugh.com>
Cc: dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com>
Date: Mon, 1 Feb 2021 17:42:25 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/y3BHNo1XsL8CjsvIqaZ6hqVqfNM>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 01:42:30 -0000

On 2/1/2021 5:38 PM, John R Levine wrote:
> So I would say that from my small sample, a lot of people have figured 
> out how to send aligned reports,

and, to be thorough, some/alot have not.


> either by using their regular signing engines or with an SPF record 
> for the host that sends the reports.  On the other hand, for reasons 
> we've discussed that are evident to anyone familiar with DMARC, 
> there's little reason to worry about fake reports, and authentication 
> doesn't help even if there were.

exactly.


> If we want to document existing practice, I guess we would say that 
> reports should be authenticated and aligned if practical, but it's OK 
> to send them if not.
exactly.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
dave.crocker2@redcross.org