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

Dotzero <dotzero@gmail.com> Tue, 02 February 2021 00:06 UTC

Return-Path: <dotzero@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 533263A15D9 for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 16:06:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, LOTS_OF_MONEY=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 bW10RaxBZxLH for <dmarc@ietfa.amsl.com>; Mon, 1 Feb 2021 16:06:10 -0800 (PST)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 E94E63A15D8 for <dmarc@ietf.org>; Mon, 1 Feb 2021 16:06:09 -0800 (PST)
Received: by mail-qt1-x832.google.com with SMTP id c1so13775475qtc.1 for <dmarc@ietf.org>; Mon, 01 Feb 2021 16:06:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=OWd/ZFn/T1XAEeMYi3xUK3CSp0mp0DY7JiBmNh25xDc=; b=oSTipLKwouoRMlqiK3zdspqUsHRpP7hI7A207PMDp3S9+F9fqeNAf/+xpE5fcAimW8 sXYeiLWOSqctLlcRa/gjdC7c3k0Qg2elrR9ZR0NY29YdaN/xlRDDMS8OuQJTxfTNcNxG vmN6IWMUJDc68f3+fvkFfF7hBEI3hLGCYujOY4NgJawqXG4y+FmR7Kn+j9XZXAG9/Qqi ejjfG1DXymD3XX1dsAj/5mX+PU27FRmj5LrqgPnQGJuGOL4YaGnelitxHBGvzHzh9CBV SPcG82X/5iGITDsh1L7zzkiyNO+7QFPRcaKRELDDvqvfLR6g/IjL6bRb4hJ4gjInaQrK pXUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=OWd/ZFn/T1XAEeMYi3xUK3CSp0mp0DY7JiBmNh25xDc=; b=ppxe0XF/nBz65zw4BJthZJrtMG6QwxFieMXvSp/0XvHluygZHCL+wqfZH6odcODSll i+caW0XPyaJ/vRFMibAkap6/zWNVi4t/pyxEMJ07AdkFHa36jVOKz1LvZb7IDkVvxrtM P38vEDl2h+zUYZUA4Ulg2h+9MSx5bBw7RLMs7p0+bzBMVOgYdmuRuw49Y30D7ie8jfPg v0qFUAFBdsei554pyzA3bs5s1669V20yYAKEj8xE1nCEPDkMG5bkvrTDKu57tx/HwCUA lG4frgYbVDboRmaTMwNpAUVqwV9R3kqtJcn0xoGxcp8+paE6wqfYDXKftSSwjrL7q4UG zafw==
X-Gm-Message-State: AOAM53161uiCnvtQZjdz04bs3si751IRvbOwROoYgM+2CKYwVdSr1KFc sTUfnEWOCbDVYGS/Z/3IMP1A/te/1OtY2j9YTRWD9xIe
X-Google-Smtp-Source: ABdhPJzcLzlk+nGP/8OVyeuI8OXC/NQfi9Th38WBsSz5zMFBtHRu7mRzqlbdBRrVkjmdFowY3b9Ff58MUTPvVAFjqoQ=
X-Received: by 2002:ac8:564e:: with SMTP id 14mr17701224qtt.286.1612224368310; Mon, 01 Feb 2021 16:06:08 -0800 (PST)
MIME-Version: 1.0
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com>
In-Reply-To: <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com>
From: Dotzero <dotzero@gmail.com>
Date: Mon, 1 Feb 2021 19:05:57 -0500
Message-ID: <CAJ4XoYeHxhZyAsMBJfjDn7XFSeFt39agjoFQRBTbMZ0zdvaLyg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c57b7305ba4f3ce7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/DgPYnwL9XBJZVawZdrnz1Z43YN4>
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: Tue, 02 Feb 2021 00:06:11 -0000

On Mon, Feb 1, 2021 at 6:49 PM Michael Thomas <mike@mtcc.com> wrote:

>
>
> 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.
>
> It doesn't strain my credulity at all. You are assuming a single mail
stream. I saw it at my own employer before we got centralized control of
DNS and implemented email authentication. I actually know of one company
where several hundred thousand dollars of marketing emails ended up not
getting through because a marketer thought they could evade corporate
policy and the ESP gladly took the money even though the mail was getting
rejected. It's a crazy world out there.

Michael Hammer