IETF Logo Mail Archive

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

Michael Thomas <mike@mtcc.com> Mon, 01 February 2021 23:49 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 BDEEA3A15B4 for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 15:49:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 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, 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 lSpnUHZ0XUj8 for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 15:49:42 -0800 (PST)
Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (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 298713A15B3 for <dmarc@ietf.org>; Mon, 1 Feb 2021 15:49:41 -0800 (PST)
Received: by mail-pj1-x1029.google.com with SMTP id g15so974171pjd.2 for <dmarc@ietf.org>; Mon, 01 Feb 2021 15:49:41 -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-transfer-encoding:content-language; bh=1pu/gpJIPnjgNXy4OCHsClZfcuqbxUKzMtyAmaV+RI0=; b=nmGFNRD/926PTp3c4/Swl09UmndFIES5Qi1C8yfoYELGDRPc25TqPjwgT1W+6H3k13 WLVF17GGLtLjJ2t7/FYLOBgnguDYKt8bzo/WjacqheMelYMVBTrv2SjGykL5Izcqxjp3 e82pzskXYZGcKilEQUL9YGyqwteQsWtNN7j2L0RnwplMBbDbSF1LSbT89A6UEpP2ZvZQ 3CXbJeeYSOxfy04oXGaEbX6ISs3018jUVjnK3tKbJ3edDn5q1Po2mYuA58MMyitrBflx i8rqL6sLnOqMYi6dbkFr1P0D1IlsahUo13Wnm5z5DtTr2FWjiiSpLEOq7tux+aT3QpIP S72A==
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-transfer-encoding :content-language; bh=1pu/gpJIPnjgNXy4OCHsClZfcuqbxUKzMtyAmaV+RI0=; b=fv/BVEiY4EKfHTU45AqBG2STiyhowNi4SGEY+FeihKoeSu2eb+kXp9DLpu1dJpf1L7 cUIU2MZKEtMBJ2hsjkXB3pxGMJvKsFbdP1pBTKsz/PSDXlbfx/quVkHhHg7sVbYT3RRE ItH4G6KmxwHoNcRPfbA2GlmyG9OzzSBOazOJCglpdWLBfw7ILEVpHU4FcM9PyGUWZcyo JZ2SQK7eaMkYKr+hk/UysMuVKtnTz+VneVs1OYVXX1bn2kseT8KPMouu1L3Ak73TXBqS fwcJOLXYvmv0tfxZGrT8P9T/ljc8C1BkHBYxs0qeVruJGa57JkLtghjAoFm214lBPjpv 5Gwg==
X-Gm-Message-State: AOAM532OpWnHybmeWgyrET0pbvXLUchyKrXi6YfEGu7briCuZIGYM9tL /pKPtSUKiw/IXByCyzTjvnmdAvwk7tevQw==
X-Google-Smtp-Source: ABdhPJxkCU5FWyjZRWhSoLOmjvgn5+YRM92ciAyZV7V2sdTtzsWfv5a0CyxBpbXvUuu/pPPJ1B+Qgg==
X-Received: by 2002:a17:902:b285:b029:e1:5b44:454 with SMTP id u5-20020a170902b285b02900e15b440454mr7132992plr.54.1612223380901; Mon, 01 Feb 2021 15:49:40 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id mv14sm970734pjb.0.2021.02.01.15.49.39 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 15:49:40 -0800 (PST)
To: dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com>
Date: Mon, 01 Feb 2021 15:49:37 -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: <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/5GjnjAbzFpES0dMU9ghaj6QY5pA>
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 23:49:44 -0000


On 2/1/21 3:23 PM, Dave Crocker wrote:
> On 2/1/2021 3:21 PM, John Levine wrote:
>> I find it hard to believe that if you are going to enough effort to
>> maintain the data to create and send reports, you can't figure out how
>> to install an SPF record for your reporting domain.
>
> Except that the tracking/reporting functions are completely separate 
> from the 'signing' side of DMARC and could easily be different parts 
> of a company.
>
> d/
>
It strains credulity that one part of a company would want to send out 
reports when some other can't even sign their email. Both need access to 
the email stream for starters.

Mike

v2.23.0 | Report a Bug | By Email