Re: [dmarc-ietf] Some Proposed Language for a New pct Tag Defintion

Todd Herr <todd.herr@valimail.com> Tue, 03 August 2021 12:08 UTC

Return-Path: <todd.herr@valimail.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 29FC33A210A for <dmarc@ietfa.amsl.com>; Tue, 3 Aug 2021 05:08:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=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=valimail.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 bt3MMCJ8n4_B for <dmarc@ietfa.amsl.com>; Tue, 3 Aug 2021 05:08:36 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 0C2193A2107 for <dmarc@ietf.org>; Tue, 3 Aug 2021 05:08:35 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id g11so13735106qts.11 for <dmarc@ietf.org>; Tue, 03 Aug 2021 05:08:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wWgi+3/gd1xdXJqWcGBJGi+/6B4DfyYGnrBSDSaG9Go=; b=CxOCDFUjFJDlMrwo8q0KMGEH14cGlGxg8ZKt4GBs9kZZB5jsKTXpFGuzL2VGl3dY6R 8UupxD/npQk2voKeFuVN+HnEqtQiI2wPvA6za8/Nm5V8WhqK2k16NWaWZaUnDnDl3KOx m2gYjbztdZxh34SknKRA9++YdRDizvhrsnfcT4+s3mO8xUmzw3TOqy5Peyfab7lC1Wyw A5L1vMOc4DyhoQPc8aI9iHpj6+xAv4mSBRWqUH21m+8PzkDsVQxFFsfrvEUZ88SQKaG0 Duy/IMfUVewpHxwKvS4wmrXP7v/x5kEvASuHUKTmShY424ONY+DjiddTHGQSbXo6+2Sz HA2A==
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:cc; bh=wWgi+3/gd1xdXJqWcGBJGi+/6B4DfyYGnrBSDSaG9Go=; b=m9V8f75oDTBZ6Z1vVf6hOj9BII+4PKmcVdC154lHxRrnZKXZOdA5zM59449EGPXcEK gppbk9cHBV1YMxrJGC+PYDHGVf5QVuA7cdiKG/Jv+3FVQIxe5WHntQ8XQbBU9yZSMTUW 1rLPAADkqshjqVOPKjjkBNpHPQ53leoFgpg56JsV6CtOvO4Po5GfxF3SyaaTPr+EGzBq gV3jcvS9xHBw3bdmj2/y9DBvhgvT1eDvhUUUiezfT8FWIw7BnH0cmK/Dzrtt2Rg0G+X6 5JICj9+MNdcHCblxiVBG5OkEssciU95vs2kD+zRzKJbbUn8fDW7KnrUee0xla2v/0wy1 M82A==
X-Gm-Message-State: AOAM533VpSm6DqBBaSctOKsz6qnaowJ/kt82IchlLTZR8YrLAMm6sbzs FpFX0ckoE5cmqiY6x+MUXwULiHdQhfVHdq0PbJaJMj5isw8=
X-Google-Smtp-Source: ABdhPJxgeCk4bAJZlMnewG3f4o644KoTW5yB0cBI2tnKImkdft9wLRGrg7PCOvf/fFssca/lx4W4rUJdwDQXsi4TYzE=
X-Received: by 2002:ac8:7695:: with SMTP id g21mr18507937qtr.83.1627992514433; Tue, 03 Aug 2021 05:08:34 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=LL_KWcVYnc2quYSGMnQF5bdoerDtTZZm1yGjxjCqW1Q@mail.gmail.com> <20210803021005.EE5CF257D352@ary.qy>
In-Reply-To: <20210803021005.EE5CF257D352@ary.qy>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 3 Aug 2021 08:08:18 -0400
Message-ID: <CAHej_8k0rZHY02_mAMfc19dUOVREbd_WdTr5whUuNHmggx+cdA@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000085282905c8a68b5d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/v6gaB2iQNEzGzlqVAZ_8f4xD4wM>
Subject: Re: [dmarc-ietf] Some Proposed Language for a New pct Tag Defintion
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, 03 Aug 2021 12:08:41 -0000

On Mon, Aug 2, 2021 at 10:10 PM John Levine <johnl@taugh.com> wrote:

> It appears that Todd Herr  <todd.herr@valimail.com> said:
> >> I like simple, but I also like the idea of a separate section that
> >discusses the history of the pct tag and why the old values won't work any
> >longer.
>
> OK except:
>
> >   remains the default, and "0".  The value of "0" took on unintended
> >   significance during the experimental stage as a value used by some
> >   intermediaries and mailbox providers as an indicator to either
> >   deviate from standard handling of the message and/or to alter the
> >   substance of reports generated, ...
>
> Alter the reports?  Huh?  I was under the impression that the policy didn't
> affect the reports, much less the pct.
>
>
My apologies...

My memory of the effect of the policy "p=quarantine; pct=0" vis-a-vis how
Google handles a domain's mail was faulty. I remember when working to
implement DMARC at $JOB[-1] for our corporate domain, I was seeing data in
the agg reports from Google when we were at p=none that led me to ask "WTF
are those hosts?" and digging around the various corners of the internet
unearthed the unknown at the time to me fix of "Yeah, you gotta be at
p=quarantine; pct=0" to get reports from Google that make sense.

There are several years old threads on mailop that speak to this topic,
with outsiders asserting that what is in fact happening is Google Groups is
rewriting the From when it's p=quarantine; pct=0, and Brandon Long from
Google in the thread doesn't challenge that assertion, so I'll remove
reference to the reporting alteration.

-- 

*Todd Herr* | Technical Director, Standards and Ecosystem
*e:* todd.herr@valimail.com
*m:* 703.220.4153

This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.