Re: [dmarc-ietf] Search for some consensus, was: Proposed text for p=reject and indirect mail flows

Jesse Thompson <zjt@fastmail.com> Wed, 26 April 2023 21:53 UTC

Return-Path: <zjt@fastmail.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 7FFC2C1516F3 for <dmarc@ietfa.amsl.com>; Wed, 26 Apr 2023 14:53:55 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=fastmail.com header.b="FA1KkhuG"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="OS4V8iRM"
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 oeFY0EXIuVsW for <dmarc@ietfa.amsl.com>; Wed, 26 Apr 2023 14:53:50 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7B7AC14CE39 for <dmarc@ietf.org>; Wed, 26 Apr 2023 14:53:50 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 27D89320092B for <dmarc@ietf.org>; Wed, 26 Apr 2023 17:53:50 -0400 (EDT)
Received: from imap42 ([10.202.2.92]) by compute1.internal (MEProxy); Wed, 26 Apr 2023 17:53:50 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1682546029; x=1682632429; bh=Dg h2Ak2eTw42FkIIl4xILzTLuTq0spSAwhT+TkBzuJM=; b=FA1KkhuGGNCR8w1kEt rB/CfT5jzC09pCK+QxTw9SoEzgGg8MpfniL1vtO6AL5q+d+jpTF4gDQBqDzE3nYq qJbtQWsrVhIGs6Esc33pX+ZNuHbt+KC3+3O4DEfNRBELYdmUHB3uuXU6/lxgy+bO be/F/BC7BjY/qn1orDi4WuXYRGjbGE4RI74j3/F/XLzwMVupFnT/ziB6Cp9UmhJ7 KKLg3yr2WDHb/u/yocunwrcGJ7G22S+X2JxBrk7hMdvqnFSKRrOTvilCzuH5cxgM B8Cqns50k0TgLQrYHSuYLGz7kKEdrRyjv4hKY7uJEkCylTzMKnMObzOgjw8bceoM ZF0Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1682546029; x=1682632429; bh=Dgh2Ak2eTw42F kIIl4xILzTLuTq0spSAwhT+TkBzuJM=; b=OS4V8iRMSRClHFjV0RIZbqK9DAxfg Tz5qKNWGXsmXTasFFp1tEH3GV9kPrpLOq++XkLQ9obsWhwx+F/A10pRSQhFuEOf4 VJ71Vzbggqsz8nh0EvtfQeMCpOJnTxqiYjKo/yt/UUa5fXsdjkKQEwFjlKLRrvDN i5lM1dhS9T9gyJKWZpU0STMd3DGiobtpYY24rOI4iAJzOd+YEHKJZjGRnD4ct6gc FarUPHCJV9+ZoqDWkcg2jkg6yDc0VhIm3c9WxRQ0PJJTwC1jCbmDQMXZJtjASRQC VPmr78YFqqrYTirbfpHr7KWHFUnovAppet31m6CLfaorB9PgbwFgcKIOg==
X-ME-Sender: <xms:bZ1JZF0rsZPNlEFmL3adgQHueGBzcffV99_dIVMEzwiJbjSLePuxTg> <xme:bZ1JZMEgF_eWlL-sMLe89legdnsSmfGN5KUErM7DJ7ZoF2oBXK0K40Y6e_cHf_idZ 36k3irp1SxOnc55Vp0>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeduhedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedflfgvshhsvgcuvfhhohhmphhsohhnfdcuoeiijhhtsehf rghsthhmrghilhdrtghomheqnecuggftrfgrthhtvghrnhepgeeulefhfedtheeguedvud evkeduveelffevueehuddutdduhfejfeegleffieegnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepiihjthesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:bZ1JZF6wkoNbQTGPesBUzr6uN53Z3ejzb33MXwIVeG3gh24CuETjlw> <xmx:bZ1JZC34dC_2bgJ5kUwwu87ZZUnLLDUS2HYNEJ2YtgxlEcD0Q8s1fw> <xmx:bZ1JZIHdhVdBW6Lg74hTvKphu_95Igwrwwi5poeCiVF8EYVtSHWCBA> <xmx:bZ1JZMTEhqfpqqw9-SGgqyJUa8DphLrXcqYYzisqNm8TJBejRwxacw>
Feedback-ID: i1a614672:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 8B616BC0078; Wed, 26 Apr 2023 17:53:49 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.9.0-alpha0-374-g72c94f7a42-fm-20230417.001-g72c94f7a
Mime-Version: 1.0
Message-Id: <7ff25a96-b6ed-4999-9315-a236bfeaf069@app.fastmail.com>
In-Reply-To: <D29CB79C-AAEB-4999-92C7-D19389916D98@kitterman.com>
References: <CALaySJ+NBg9vzqa0_t-sBf7EKXQ3A=DTyy-Vc7M-ZK9-vfJxmw@mail.gmail.com> <29216533.CRhL9lMF2B@localhost> <9aaeadee-c29a-efe8-2c43-ed6fc1b3ed0d@tana.it> <D29CB79C-AAEB-4999-92C7-D19389916D98@kitterman.com>
Date: Wed, 26 Apr 2023 16:52:29 -0500
From: Jesse Thompson <zjt@fastmail.com>
To: dmarc@ietf.org
Content-Type: multipart/alternative; boundary="1671d5efcc194c9e96b1704f15f6ff51"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/AK9duCqBy9AG1FqzQ7Gau9WOwa4>
Subject: Re: [dmarc-ietf] Search for some consensus, was: 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, 26 Apr 2023 21:53:55 -0000

On Wed, Apr 26, 2023, at 6:21 AM, Scott Kitterman wrote:
> 
> 
> On April 26, 2023 8:08:39 AM UTC, Alessandro Vesely <vesely@tana.it> wrote:
> >On Tue 25/Apr/2023 20:27:18 +0200 Scott Kitterman wrote:
> >> My recollection is that a general formulation that I proposed had at least
> >> some traction out of both groups:
> >> 
> >>> [some appropriate description] domains MUST NOT publish restrictive DMARC
> >>> policies due to interoperability issues
> >> 
> >> Leaving aside (for now) the question of what goes into [some appropriate
> >> description] and with the assumption that there will be some non-normative
> >> discussion to amplify whatever that is and probably give some indication about
> >> what domains might do to not be one of those domains, is there anyone who just
> >> can't live with that formulation of the situation?
> >
> >
> >Me, for one.  Because more than 98% of domains are going to fall into the description, however we word it, that statement makes the whole I-D nonsensical.  Cannot we just tell the problem without MUSTard?
> >
> >In any case, using the complement of [some appropriate description] is certainly easier.  For example:
> >
> >    Forcing authentication into Internet mail by publishing restrictive DMARC
> >    policies breaks some well established patterns of usage.  Publishing such
> >    policies is thus RECOMMENDED only for domains [in this other appropriate
> >    description].
> >
> Thanks.
> 
> I understand your objection to be that the proposed description of the interoperability problems would apply to too many domains, regardless of the modifier we might use.  Is that correct?

I have a similar concern. Any domain owner with size or complexity or users (who will do what they wanna do) will easily find their domain in a mixed-use state, and (ironically) the only management/governance tool at the domain owner's disposal to prevent future unintended use of the domain, in favor of subdomains, is to publish p=quarantine|reject (throwing the baby out with the bathwater)

Jesse