Re: [dmarc-ietf] list history, Signaling MLMs

Wei Chuang <weihaw@google.com> Sat, 15 April 2023 22:18 UTC

Return-Path: <weihaw@google.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 AC347C14CE42 for <dmarc@ietfa.amsl.com>; Sat, 15 Apr 2023 15:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.596
X-Spam-Level:
X-Spam-Status: No, score=-17.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 pNpmMuF4m83y for <dmarc@ietfa.amsl.com>; Sat, 15 Apr 2023 15:18:01 -0700 (PDT)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (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 C7663C14F73F for <dmarc@ietf.org>; Sat, 15 Apr 2023 15:18:01 -0700 (PDT)
Received: by mail-wm1-x330.google.com with SMTP id 5b1f17b1804b1-3ee76561c03so605e9.0 for <dmarc@ietf.org>; Sat, 15 Apr 2023 15:18:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1681597080; x=1684189080; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zkqkk04fuUlHzmDV/ksYN+P4Wj0Pk/XyOxYAmykQHjs=; b=AmAviGi8tO6bQqTYsa4m/EShorEAlfl5KiJ81QzQbu6W64xJ9trGpe7QtTaEQb2jA7 IFkbgEoxhUC1FBk1KXdN3tX5CyqGLmW0Ssk3WqJKd8jiADLhP+zqbw6y4y9JlH5HaTax gGpwaKHW7SQPy5xwh3e987ELMKWrSw+DawINBnhl+Qmjuvr3oPYrgm6Ot3i8qz//2jLT R+3uNIMi0BhNpLbdYxITJaj3ITkFqa/pZrillAYcGzpE6WDeGQMAYNo6Rv9z4szoGZ2Z f6WH8778FKMFlOvBcxa03SApTZWrgmvozXleTfZaEJCJEyl37B7CfFSRP2UQ+nnBPymJ Um+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681597080; x=1684189080; 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=zkqkk04fuUlHzmDV/ksYN+P4Wj0Pk/XyOxYAmykQHjs=; b=G7FH6ohDfhWliV2NWgE5HZYXRezRgYw2a2HQww7WfaJxh3R+gAZ0EbvFvSodxesVRh aXmajdMcBPj4Z4ApESPbnnuSrp3vzgWqqE0DvgVMi0aF4kzRJwreQtyPYjaJ3XaRvm8l jQ3MIdoXe4g0AmlB9KxO/Q3KI/fD+mnTK4NjGooVx4hVZ8fVZZSTe8sZ5kM6divzn/x1 EVe/xzlmpYZZAOwbiBCX5o5jY2Q+iynXQXYJ6OrljNjdrqJnD46Spa4sJK1kJreJcCDy /nyqoi3aYNjEOKzEuAefjBrraMYcZsS9/oUEnTlMHplMXuvclOU9/zQT9tznC+EfjgBv veew==
X-Gm-Message-State: AAQBX9cSZq81ZMe0apGtJF0epaJOLjwF9ycTidLYk8LtOBiU3Mn/eBDl Yx+hnqpARaCu5+nhVb+DzjVLB1xEqN0zte+/Yy4XIIE5n26ZIv1/RtbkqA==
X-Google-Smtp-Source: AKy350YGHk7KEDwHA1wdnOjs+PMB98RX2aW4suIwTwdqqEUbR9ELmrb/svTdobLN3smgizFf5ShTcuMW4KLa2l+3LJI=
X-Received: by 2002:a05:600c:1f18:b0:3f0:8108:938 with SMTP id bd24-20020a05600c1f1800b003f081080938mr12875wmb.0.1681597079620; Sat, 15 Apr 2023 15:17:59 -0700 (PDT)
MIME-Version: 1.0
References: <20230415170715.10F26BF2C124@ary.qy> <b8269f1d-6b43-4be7-b6d7-edcf79c3118f@app.fastmail.com> <04cffebc-169d-dfea-e2c6-055406a74b1a@taugh.com> <D450EAD6-17F7-4F70-B4D3-1C8C283E2BE7@kitterman.com>
In-Reply-To: <D450EAD6-17F7-4F70-B4D3-1C8C283E2BE7@kitterman.com>
From: Wei Chuang <weihaw@google.com>
Date: Sat, 15 Apr 2023 15:17:42 -0700
Message-ID: <CAAFsWK1ZFURRnfqSoBnzRN9=P9XCCOW+H4kL3jrsBLYNk4SB0w@mail.gmail.com>
To: Scott Kitterman <sklist@kitterman.com>
Cc: dmarc@ietf.org
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="000000000000a1c55805f9675486"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/kqQWwiePxkJbSy12bIl2mvGh7MU>
Subject: Re: [dmarc-ietf] list history, 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 22:18:05 -0000

On Sat, Apr 15, 2023 at 1:40 PM Scott Kitterman <sklist@kitterman.com>
wrote:

>
>
> On April 15, 2023 8:17:41 PM UTC, John R Levine <johnl@taugh.com> wrote:
> >> I'm assuming that the "long list of stinky possible workarounds" are
> the existing "whatever" mitigations, and rewriting seems to be acceptable
> enough as a mitigation to convince large [enterprise] mail systems to move
> forward with restrictive policies. ...
> >
> >I think you are greatly overestimating the connection between cause and
> effect here.  The people setting the policies have no idea what effect they
> have on their users, and to the degree they do, they do not care. IETFers
> at large organizations who support their IETF work, and that have p=reject,
> tell me they've told the IT departments that the policy is making it hard
> for them to get their work done and the response is either "duh?" or "not
> our problem."
> >
> >> I intentionally published > "p=quarantine pct=0" specifically to find
> the MLMs that implemented no mitigations, weighed that against what I knew
> about which receivers enforced non-mitigated mail, and then made a judgment
> call to move forward.
> >
> >It sure would be nice if people at other organizations were as concerned
> about the quality of mail service to their users.  But noooooo.
> >
> >> I believe Wei suggested that we need to find a better "whatever" (in
> the form of an alternative to SPF and DKIM that works with mailing lists)
> ...
> >
> >I would like a pony, too.  But ARC is as good as we have now and after a
> decade of beating our heads against the wall, I don't think we're going to
> find anything better.  I've suggested a bunch of things that would make
> lists' life better, and nobody is interested:
> >
>
> Agreed.
>
> If someone has a great idea for a third way in email authentication, they
> should develop the idea, get some deployment experience, and then document
> the protocol.  After that would come the question of adding it to DMARC.
> This is not the working group to do that work.
>

Agreed such a proposal shouldn't be worked on in DMARC.  Also agreed that
it's a good idea to get deployment experience.  That said, I think there is
a lot of value in getting early IETF feedback in some other
forum/mailing-list to help review the potential proposals.

-Wei


>
> Scott K
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>