IETF Logo Mail Archive

Re: [dmarc-ietf] Signaling MLMs

Scott Kitterman <sklist@kitterman.com> Sat, 15 April 2023 14:28 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 C9353C152573 for <dmarc@ietfa.amsl.com>; Sat, 15 Apr 2023 07:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_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="3ubF6sds"; dkim=pass (2048-bit key) header.d=kitterman.com header.b="P9F+1Qrk"
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 IHXI0Gfoxn3Q for <dmarc@ietfa.amsl.com>; Sat, 15 Apr 2023 07:28:51 -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 1E239C14CEFE for <dmarc@ietf.org>; Sat, 15 Apr 2023 07:28:50 -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 7DCB4F8029E; Sat, 15 Apr 2023 10:28:38 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1681568903; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=uUjefBzidD6qsdjNVb549Nl8ILMKyiyFGrz+yN+7Ha0=; b=3ubF6sdsxsvIBb+55EvZ2eK2kcL4r75rJBxEi1ycqLu6kDQGuzUJvO2M2mrsMhCDdLn54 tmTCSQYo0w071MGBA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1681568903; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=uUjefBzidD6qsdjNVb549Nl8ILMKyiyFGrz+yN+7Ha0=; b=P9F+1Qrk/ugG8/pYTxUgEPGBrLA71cJXIZ+sWDuTXxHjRXParohwG3aH2noo/EIuUlxxS 38D/Y2qZ9Ikxpw6jMNpq9+wd+EUXuKZ5pm5R1JXrYbiPTlEZzzxDEOsxxE1J0Ep+tBVTesv sS5QextG0jHrmcJYkS14JYDf+d1Wtw83D91HLtCCcIfB7wThfHOFISKohBw2wsifjgIQ77d CtbRfh589MWa5Gihyx5CknikGVISuQnLCz/3drYOIWM6401Xc/5L+HxiEiuEwLaD0TAhuu1 5feDnEpbgp/iTh3x/jwes4bqFd9EFa0CLumLOxle1cwGPNlpSGINgIB7y0Ig==
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 F18EAF80221; Sat, 15 Apr 2023 10:28:22 -0400 (EDT)
Date: Sat, 15 Apr 2023 14:28:17 +0000
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
In-Reply-To: <0FF652CE-083B-4C7C-87D9-30E4F03FDBA2@wordtothewise.com>
References: <19178820.EVbMYgQtk6@localhost> <0FF652CE-083B-4C7C-87D9-30E4F03FDBA2@wordtothewise.com>
Message-ID: <FAA07113-9BEE-4C45-A017-5C88EEF23C6B@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/Fts4HznUGFYs8pLgz4RrN-274tI>
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 14:28:56 -0000


On April 15, 2023 12:26:16 PM UTC, Laura Atkins <laura@wordtothewise.com> wrote:
>On Apr 15, 2023, at 4:25 AM, Scott Kitterman <sklist@kitterman.com> wrote:
...
>> Or [person] gets a Gmail account for his IETF work and doesn't bother tilting at 
>> windmills.
>
>That solution only works until gmail publishes p=reject. At one point they said they were going to do that. 
>
>It seems to me that there is zero harm in actively documenting the problems with DMARC and making interoperability recommendations about who should and should not be publishing restrictive policies. 

I agree on documenting the issues with DMARC and making recommendations to improve interoperability.  There are issues and they're significant, but we shouldn't catastrophize them either.

To your other point, if that happens then people will move to another provider if it affects them negatively.  If free email providers that don't have p=reject get hard to find, then that probably creates a demand signal and some entrepreneur will fill the void.

Scott K

v2.23.0 | Report a Bug | By Email