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

Scott Kitterman <sklist@kitterman.com> Thu, 27 April 2023 05:07 UTC

Return-Path: <sklist@kitterman.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 42481C151B08 for <dmarc@ietfa.amsl.com>; Wed, 26 Apr 2023 22:07:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b="XAg/2iuB"; dkim=pass (2048-bit key) header.d=kitterman.com header.b="YEpHx9Ll"
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 C8PanDX2Ml5Q for <dmarc@ietfa.amsl.com>; Wed, 26 Apr 2023 22:07:44 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 AC578C16953D for <dmarc@ietf.org>; Wed, 26 Apr 2023 22:07:33 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) by interserver.kitterman.com (Postfix) with ESMTPS id 904F9F802E3; Thu, 27 Apr 2023 01:07:19 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1682572024; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=UWyx0UFQ83QiQbokP+1zIGPKQNzXMHcWke9MP+IfHMU=; b=XAg/2iuBt1V3v0rwm0AcZwyGqReUFsUomLAg/byMvRncgjt2fJByzFjh5n4POLSvNSD55 G+0NYmza/VnJp0vDw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1682572024; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=UWyx0UFQ83QiQbokP+1zIGPKQNzXMHcWke9MP+IfHMU=; b=YEpHx9LleO7T0FqJNa4Ch44l42+SqkWdEzD3tDfjRHiqtpxmydDoT4pKigFYUZYNW/QMj GpcN6K68tCAkb/2rk3RqyVcp8l4liTZ3T5UGcnNe4/f1jX/TfvYVfMfh49njm4yrCdnXI67 NLbLODyHhyJ9VCkmXR/IBYFZ3wh0AgJoiOktYuz8FmgnkwabH+V21BjLZlNMqAJM517qmde Fit57aEC6tbDHgUp51um8bt0H7sk9bURv9GYinrNySkhmFJHoE+a3y8OvHituXB4EHiwbDF G7wUhMIYnbrilKwLT8Ke0Qpw+KI/zPlRi/1M2Tab+BOLDZ4I45YC3m+AtmfQ==
Received: from [127.0.0.1] (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTPSA id 718FEF80057; Thu, 27 Apr 2023 01:07:04 -0400 (EDT)
Date: Thu, 27 Apr 2023 05:07:01 +0000
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
In-Reply-To: <B08C7AD1-B14B-43FC-BE85-DFBD5282A8DB@bluepopcorn.net>
References: <20230426160609.8532BC586620@ary.qy> <B08C7AD1-B14B-43FC-BE85-DFBD5282A8DB@bluepopcorn.net>
Message-ID: <BF125E76-EAEF-468B-93F2-3318736F932F@kitterman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/j0RZkQX9jfI6_Nrs7uQ5SW651-Y>
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: Thu, 27 Apr 2023 05:07:49 -0000


On April 27, 2023 2:32:49 AM UTC, Jim Fenton <fenton@bluepopcorn.net> wrote:
>On 26 Apr 2023, at 9:06, John Levine wrote:
>
>> It seems to me there are two somewhat different kinds of DMARC damange
>> that we might separate. One is what happens on discussion lists, where
>> messages get lost and in the process unrelated recipients get
>> unsubscribed. The other is simple forwarding and send-to-a-friend
>> which gets lost but is less likely to cause problems for the
>> recipients beyond not getting the mail they want.
>
>Isn’t (in the latter case) the recipients not getting the mail they want exactly an interoperability problem?

It absolutely is.  The difference, my view, is that if the domain owner has a policy that leads to you not getting your mail, it's a different level of severity than you both don't get your mail and end up unsubscribed from the mailing list.

One might make a case that the former is "works as designed" since the sending domain owner has published policy indicating he doesn't want you to get your mail and your mail host has decided to honor that request (I think that's wrong, but I can see the logic).  I don't think there's any way to claim third party's getting bounced from a mailing list is OK.

Scott K