Re: [dmarc-ietf] Proposed text for p=reject and indirect mail flows

Todd Herr <todd.herr@valimail.com> Wed, 29 March 2023 15:35 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 A6CD9C14F736 for <dmarc@ietfa.amsl.com>; Wed, 29 Mar 2023 08:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sukLKP8ZkVk for <dmarc@ietfa.amsl.com>; Wed, 29 Mar 2023 08:35:50 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 504EAC14EB17 for <dmarc@ietf.org>; Wed, 29 Mar 2023 08:35:50 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id ix20so15317601plb.3 for <dmarc@ietf.org>; Wed, 29 Mar 2023 08:35:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; t=1680104149; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=m3f9jFcFeKu+Eep3wrcom0/QuWvZgDJZjLtNRGCBLes=; b=aOuYpHu8HyHAhvtRWS5I8ZPybOvL2Xg9+r86ewsRkgXQKHGpd6s4ENg1RplyyRZWE6 Vx1kVjGCIxwSoFKPvYr0+3KbIOd0nIlRu60oCFP6WGzXRW71RWngdJYCKPL/q5vahVMo yDjUkJogB/fjk5XD+QcXQ+0ecl00zmLTge4b2ImILzBUAeIzmGOEUazPB4jIAxgn0h6k Zn6bvhYX4b+gzoj8WzDPFSOMxcdLNq6lfoq8lO6xX/62tv22ENEpHCi7qFEJLtwrZhnJ r+D40poJHHUJCFAIcG7dgiJVkaljf/jHX0DGqfrJGic+nvJzxizrQqQTbwUVa0kQzRC3 73ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680104149; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=m3f9jFcFeKu+Eep3wrcom0/QuWvZgDJZjLtNRGCBLes=; b=PuYGwi94dI6/po9wEWijF4frAhBbm/NpOdbM6Oox9OJ1uq3nEgwVxVaVET2ueszEZM cTga5DCq2qE8kC3I4p5H4op9TnYID6vICp2XpJ84TDMwsRcYIqKBhfuQhEbWhSl0TVeP oTO3KKrv3m62AnBK4mV2nSi3RrmXvTQHT5KxVHq9AwKYVXLbzxh5k+N9NKCLo27TdBCU pxhARlISMO3gab4nWuqwkc697GNJcXecxfFd8eWp6A4OvxUhNG5XJ5+lrtmvPFEPibLz m/94FVI1wfNaxGkZRUPEUlYPonh+Y44WasPLvblPlljRyQeTSP3ibrV1edXMsSaszjzS PlVQ==
X-Gm-Message-State: AAQBX9fMcJldpDJQ6MHZ6DPGfoiXgcNpUwRmWERP7l3vdO0DpO72JkdC +c/qp/b4C2xGUhLasw/djTg1gSiNUsCTKyIjdfy50YaQbALrPjOV
X-Google-Smtp-Source: AKy350ZBjRvq1BUfSf0b55Js2vmswXH91CEk5XSllR2ZOjTqI/r/xA5E8LdsiroE9dtFn+mfxmqJ48FtJP0Ewf2o2pY=
X-Received: by 2002:a17:90a:cf09:b0:23b:3d0b:f162 with SMTP id h9-20020a17090acf0900b0023b3d0bf162mr5954611pju.7.1680104149085; Wed, 29 Mar 2023 08:35:49 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJ+NBg9vzqa0_t-sBf7EKXQ3A=DTyy-Vc7M-ZK9-vfJxmw@mail.gmail.com> <6319292.vCqnBZbX7o@localhost> <CAHej_8nd1xyAgwASLJbuJHyXEAfHbjqxNH1XtJxKFyfyOneyug@mail.gmail.com> <13145172.pEV04Z3DvM@localhost> <CAHej_8msLJQ0vbZ2jzitjxrQ1wdim5bHJkiD-QrU5F0EJvQp0g@mail.gmail.com> <FCFEB95E-63F9-46C3-A5F4-FA6B02FA8EB5@episteme.net> <CAHej_8=GbmzyXaeEkyLkv6uKc0-owuMC6UspPNq9irT7nF8b7w@mail.gmail.com> <CALaySJLmRyyBLE7ZKy88XUS_hXr9M2uwc8jOCYBrBPeC+pCdCg@mail.gmail.com>
In-Reply-To: <CALaySJLmRyyBLE7ZKy88XUS_hXr9M2uwc8jOCYBrBPeC+pCdCg@mail.gmail.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Wed, 29 Mar 2023 11:35:33 -0400
Message-ID: <CAHej_8mjL1YsFcCJrFXKFF70Ozw8qpJtDfUf5_Hb8n6O+Msavg@mail.gmail.com>
To: dmarc@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fe073305f80bbaf6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Zx4FnQLzhLjxBnArZqvEWF7qy10>
Subject: Re: [dmarc-ietf] Proposed text for p=reject and indirect mail flows
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 29 Mar 2023 15:35:54 -0000

On Wed, Mar 29, 2023 at 10:15 AM Barry Leiba <barryleiba@computer.org>
wrote:

> I'm very much against text such as this, as I think it encourages
> deployments that are contrary to interoperability and to the intent of
> p=reject.
>
> I contend that p=reject (as with the similar construct in the older ADSP)
> was intended for high-value domains and transactional mail, and that it was
> never intended for use in domains where general users send general email.
>
> I stand by the MUST NOT that I proposed.
>
>
I wonder if perhaps you might define "high-value domains" or restate your
position using a term other than "value" and its derivatives?

The reason I ask this is because your contention could perhaps be read as
"low-value domains MUST NOT use p=reject because their mail won't get to
its destination" and that seemingly ascribes a value to their mail that
might be considered somewhat higher than "low" in the eyes of some
beholders.


-- 

*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.