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

Michael Thomas <mike@mtcc.com> Mon, 01 February 2021 17:12 UTC

Return-Path: <mike@fresheez.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 83F953A13AC for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 09:12:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.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 0znMvESyhrXl for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 09:12:51 -0800 (PST)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 CAA513A1393 for <dmarc@ietf.org>; Mon, 1 Feb 2021 09:12:47 -0800 (PST)
Received: by mail-pl1-x62d.google.com with SMTP id b8so10351072plh.12 for <dmarc@ietf.org>; Mon, 01 Feb 2021 09:12:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=UqcwetRIyx3a/jnqWCgAFc9YOMt+M3osbsAVwr0Fm4o=; b=MIXHBAbqCHJccHnL6l20gNFcueOOCRmXDLPRHJxoflnlWhga0WQEadFZUzsrC1sGus LdLK3b2ZvgrsbYnoDCtdOp4g/JyRjIXhQJ7PDH45ksfRWGkyk44rvI+RZGoJqwQbZ0fT R2jSPK5RdPuS+5S04EgUR2jxTcAaxnCrf+C2XlL+nq34DILc+ZWSuFUOjXPU98uABCLX EzrszSLm+J7+KN8lMUUHFJoEd/9ytb6MYWgsriwh6TaqWsB0ODSTEtBACSAQCDCigKAB O1xA/XS1B/mYr7VdOzJroavou8GZ36Et1AGSUwbDX0t8JCoyWEdawTQM0WnLz72R0CTB eSww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=UqcwetRIyx3a/jnqWCgAFc9YOMt+M3osbsAVwr0Fm4o=; b=RFMg4FinRJGxXAeAPe87R6Nx5n0xSjeLEsQ1WgV714pt1liz5H5d9qAewGxQunKGiK gKG1KUUyy0/7R+EOGl7GzJFElUfIKNXRZ6kcnkaGO1QE/DVnyOSUrT0bE9M6pbIuSP1u d5ODP/5rHQMs3tPlCLMPkRW+Iyc7pOqMuh03/NtfHyyLFCBp4oJVQuaLYZWsDp3mmRn+ lyr3TexmZEBLtR6e6JkajDOTLjo64lo+HeVsqbo43RGgfq3uVen3qb4Ht2+KTKo/pn1J STTBlwApvauLl1HlPfyLBYcOTGwocbhflc/WO/m6c5ebX4F5R+VcUeAtdFAvhAi6k/ma FRzQ==
X-Gm-Message-State: AOAM530L33iyuV+sKROopxIz9lQ3utYtgicjHFfXnbo2mNRhk66XEcII +Ks19hcjexKMPZd2GVw9f7zP2dbXGP3g/A==
X-Google-Smtp-Source: ABdhPJycsh+kE3g64/Qmnfg/W41oHErllHm92eelnXeodK8QWfFb7e4qcbrB5/4AeAk6QuXvpUhCOQ==
X-Received: by 2002:a17:903:22c2:b029:de:45c0:69f2 with SMTP id y2-20020a17090322c2b02900de45c069f2mr18546866plg.26.1612199566830; Mon, 01 Feb 2021 09:12:46 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id m1sm16855963pjz.16.2021.02.01.09.12.45 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 09:12:45 -0800 (PST)
To: 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: Michael Thomas <mike@mtcc.com>
Message-ID: <316980c7-631c-4e94-c22d-7d23e99baa36@mtcc.com>
Date: Mon, 1 Feb 2021 09:12:44 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; 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: multipart/alternative; boundary="------------32D4428E028222CDFD804A72"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/XGtf5sPMCICA6vIO2vAW9qaiLk8>
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 17:12:59 -0000

On 2/1/21 8:38 AM, Dave Crocker wrote:
> On 1/27/2021 7:17 PM, Steven M Jones wrote:
>> 3.3. Transport
>>
>>    Email streams carrying DMARC failure reports MUST conform to the
>>    DMARC mechanism, thereby resulting in an aligned "pass". 
>
>
> Mostly this will discourage reporting.  Legitimate reporting.
>
Versus illegitimate ones you'd assumedly want to ignore.

Mike