Re: [dmarc-ietf] Signaling MLMs

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 13 April 2023 15:54 UTC

Return-Path: <superuser@gmail.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 EABB0C151B01 for <dmarc@ietfa.amsl.com>; Thu, 13 Apr 2023 08:54:27 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 YuTFpoz2CfMi for <dmarc@ietfa.amsl.com>; Thu, 13 Apr 2023 08:54:27 -0700 (PDT)
Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (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 64B25C15154D for <dmarc@ietf.org>; Thu, 13 Apr 2023 08:54:27 -0700 (PDT)
Received: by mail-ej1-x632.google.com with SMTP id jg21so38264934ejc.2 for <dmarc@ietf.org>; Thu, 13 Apr 2023 08:54:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681401266; x=1683993266; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pLJwE5MsYZCXsy510+h24CvVf7GjdlvC1JWcGxPHpRU=; b=OL1ATim9KgGUNChyzRT3O6QXBnWd6pV7DrZ7XKI3sxVGCxWud0oz5yrJYc/rUFWVdo 3jdU0gE2J2ksOBETGKeMK1McopBlMoSdk5RfB6NPgDaCsyhKXIonn2CZ4inJDzS0s9/a oxv/vWpKNaA8ZrpfJ0QP6Nd68KvcFemsF0gV8JYWfRIMt3e1VSnq1bgsubXZXYRL90ZZ nczYF3N3fzjn8VAQAZ08/4y1/fY6dfmvz61bhgiukDREAg4CQEzLrTu85Y2bOeLEiUqS WRQ+A4JwVtg/oFYDV+h1agElRIpK6yQFNiKB2obEiB9RgjAlDZqycH38vm8FR0aOEmQq sFNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681401266; x=1683993266; h=cc: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=pLJwE5MsYZCXsy510+h24CvVf7GjdlvC1JWcGxPHpRU=; b=CnSUDc6FuXySgN1BcDJphUpsdNg5EdIZVOgQhBLmQGHbksG2WasiTpylbWDWen/0Gf tk6n+IcKr32swU9+VwvBikX/M8MBYtOjrsHFONHy23D8AnuxvO5HjnY7xJPKmx9fRcIM l9dlKO1dRhFro9Hxo+Xq8d3vje3jYmVurOGMuqt5eIA7F2AuPjGx4SUGmciDQwMn1ii7 V8CBiMe8yRnxjpRkz5fIBau78fDlUZyDPO+st7HU8NLGNoOQU15Ul9rIZr3XLlyNFtXb xm+gW4Cr+EDlRxEIvMidjybAYmrYxlMyGWa93IWC0G1pmzJznBJvIu5cHEY2bCslL+oe o34w==
X-Gm-Message-State: AAQBX9dICwHhv30xigWM0sDZpKepJ3z6VmthKWEBEKygzO/ygrdwpzDl iJIoDMbu+JapkKa628KdS0ADs5C7oZ9c7+fH55w1Cn4a
X-Google-Smtp-Source: AKy350bhvGvOcuxTgEyGOv4cprZDEBmQXm/c49mKoaeOjZ92cZogZS5akMXCwAB2RgSXcN5VOexn/3GSRvsqV3/Q4nY=
X-Received: by 2002:a17:906:12cd:b0:94a:5bad:44ef with SMTP id l13-20020a17090612cd00b0094a5bad44efmr1604291ejb.11.1681401265737; Thu, 13 Apr 2023 08:54:25 -0700 (PDT)
MIME-Version: 1.0
References: <CAL0qLwZc2X7tyP+_8vvL3Yb7uJk6td3XGbsXUB68BNUEMhV4yQ@mail.gmail.com> <CALaySJKcf5=c_5rTiZUdRmUqsuAm0P-TykN+dew74uURRKn-5w@mail.gmail.com>
In-Reply-To: <CALaySJKcf5=c_5rTiZUdRmUqsuAm0P-TykN+dew74uURRKn-5w@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 13 Apr 2023 08:54:13 -0700
Message-ID: <CAL0qLwae4bL5NC2qY5dJVSM-MKrw7BfcL1DUUeiW_vkx_HhMew@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002b55c005f939bdab"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/_1Ysab3wG3GUgeJE7NGPYsfw7yI>
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: Thu, 13 Apr 2023 15:54:28 -0000

On Thu, Apr 13, 2023 at 8:14 AM Barry Leiba <barryleiba@computer.org> wrote:

> There's no need for a signal here: the MLM can simply check the
> sending domain's DMARC policy when a new post comes in, and
> preemptively reject it if the policy is "reject".  The IETF considered
> doing that and ruled it out because it would mean that users with
> yahoo.com addresses (and others) could then not participate in IETF
> mailing lists without changing addresses.  I think that was the wrong
> decision, but we decided on the ugly "from" alteration instead.
>

My idea is based on two assumptions:

(1) MLMs don't necessarily want to start doing DNS queries.  They operate
just fine never touching the DNS today; this is a new dependency and bunch
of stuff they have to learn to apply and suppot.

(2) An author domain can decide to affix this at its discretion, so it has
some say in which out-flows are subjected to this "do not modify"
constraint.  Of course, that discretion can lead to other problems, such as
the author domain not affixing it when it should, or vice versa.

As for the IETF, if this WG comes out with contrary advice to that
decision, we (the IETF) would have to reconsider.  It's an ugly question
either way.

I still think that outright refusal of posts from p=reject domains is
> a good approach and I wish it were used more, but most MLMs that are
> willing to put in a change to address this seems to prefer not to
> punish the sending domains users for the excesses of the domain
> management.
>

I think if the outcome is that we decide we don't want to do this, this
discussion would be good to capture in the document to indicate what we
considered and discarded.

-MSK, participating