Re: [dmarc-ietf] Signaling MLMs

Scott Kitterman <sklist@kitterman.com> Sat, 15 April 2023 16:10 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 38D11C14CE27 for <dmarc@ietfa.amsl.com>; Sat, 15 Apr 2023 09:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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_DNSWL_MED=-2.3, 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="CHXuMrNM"; dkim=pass (2048-bit key) header.d=kitterman.com header.b="ZhiVh74U"
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 GSHsTcUOqCls for <dmarc@ietfa.amsl.com>; Sat, 15 Apr 2023 09:10:40 -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 090DAC14CEE3 for <dmarc@ietf.org>; Sat, 15 Apr 2023 09:10:39 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id A4CEEF8029E for <dmarc@ietf.org>; Sat, 15 Apr 2023 12:10:29 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1681575014; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=jDPf0+SdY4s7Pyr/61e1me9xc0hEtSogElpY+zWwlCc=; b=CHXuMrNMa1ZMt87XV1RT3AuSrbaIZT9k8ZsAIi+vmPT6Uw/YumpZWq5P0fQGYJgY3Mb3i 3+RhJA7dfThTTG9DA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1681575014; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=jDPf0+SdY4s7Pyr/61e1me9xc0hEtSogElpY+zWwlCc=; b=ZhiVh74UHh0TUp9ZRZlqBULQAtPqAOaSx2lS0uukqFf3X4MtaWbK3PLAdCMV0WlKvRips 0mmU0CBhzdcOiKEGLu4RE4xzlA6aaP2yAiaW/+Uc62oug/fsuap0cFaAXKu8TQRI+GM0Mmq 0ptBONp/JUv/XuDP57Vf1GZRxc2MSr9g7q4ITADQi+k9XkivVONGUGabYJheH3zpUJ1mWTq bEgmZG7/R8xEHXFGp1WBK7j/YIbHGs4QHaA1OAYvE/t5m7f/fQl2LF01YhEPoSHKFuyRESG 20s+OFzek7EZMGWHwg8gIMwXyDRBp0u/Cm+86dfe/R58aeS+NrD05i2ecKtg==
Received: from localhost.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id 515B4F80221 for <dmarc@ietf.org>; Sat, 15 Apr 2023 12:10:14 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Sat, 15 Apr 2023 12:10:08 -0400
Message-ID: <3671459.v085TlSqb9@localhost>
In-Reply-To: <25563237-24d2-9e4f-c468-4daf8e2c339c@tana.it>
References: <CAL0qLwZc2X7tyP+_8vvL3Yb7uJk6td3XGbsXUB68BNUEMhV4yQ@mail.gmail.com> <5C458C5C-0C20-4B4D-9887-160B3048BD4B@kitterman.com> <25563237-24d2-9e4f-c468-4daf8e2c339c@tana.it>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/VKp31LkXiTmTsXSwGLk6_yA-pKg>
Subject: Re: [dmarc-ietf] Signaling MLMs
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: Sat, 15 Apr 2023 16:10:44 -0000

On Saturday, April 15, 2023 11:45:34 AM EDT Alessandro Vesely wrote:
> On Sat 15/Apr/2023 16:42:32 +0200 Scott Kitterman wrote:
> > On April 15, 2023 1:55:59 PM UTC, Jesse Thompson <zjt@fastmail.com> wrote:
> >>And the "If a mailing list would like to provide the best customer
> >>experience...MUST rewrite" suggestion seems like a reasonable way out of
> >>this "interoperability vs reality" standoff.  How about if I soften it up
> >>further:
> >>
> >>"Any sender (mailing list, forwarder, ESP, or otherwise) which is tasked
> >>to send unauthenticated email from an address within a
> >>p=reject|quarantine domain it MUST refuse to send the message or send the
> >>message using an RFC5322.from address in a different domain.">>
> > That kind of customer experience guidance isn't what goes in an IETF
> > protocol specification with normative language.  There can, and probably
> > should be, some discussion about that in an appendix, but without the
> > MUSTard.
> > 
> > As I recently mentioned in another thread, the From rewriting trick is
> > explicitly contrary to MUST NOT language in RFC 5321 on mailing lists. 
> > We should quit pretending it's in scope as a component of DMARCbis and
> > move on.
> I hope they amend that passage.  There are several shortcomings in that
> section.  By the same argument, MLMs shouldn't add List-* header field
> either.

Perhaps, but I don't think the fact that when RFC 2321 was updated, they 
didn't make explicit provisions for RFC 2919 and perhaps should have, gives us 
any wiggle room around the fact that From is the one field in the header that 
is specifically called out as not being changed.

Scott K