IETF Logo Mail Archive

Re: Fully functional email address

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 15 June 2025 19:13 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 6B043353C0C7 for <ietf@mail2.ietf.org>; Sun, 15 Jun 2025 12:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aTr1BALhyg1f for <ietf@mail2.ietf.org>; Sun, 15 Jun 2025 12:13:35 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 46100353C0A6 for <ietf@ietf.org>; Sun, 15 Jun 2025 12:13:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C124E1800D; Sun, 15 Jun 2025 15:13:34 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id alSOrATVlUtO; Sun, 15 Jun 2025 15:13:34 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1750014814; bh=r3+UrO68cgvZQHldsigTyQPCN5wQ6G/hRr41oaniqzU=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=wWVnry5WgTZ5Lhe2xiYS5+sndhBP6+nTlzoHZEh/XebV5SvjDORcQH9jwIjUPsdmV g/8ccbVx5WwRPR8wB0byPc7pav/wdzw9ZOdBh+rdwcibhZUNa1V5CN7A8mfQtRnjCy C6+h253frgvLL6+6b+rROYXC/u5ymti7m8vYo5mPQmnC0xVLC9KMUG/JmyUvkhrAZ2 Rbap+YWNyUAprmMZYxCsff3SLEZsQnYWpuhH4+VXZ77R2NZZI25WhVWjo+nDXL/CGI Dd0O1YYUCmLjoQDRKx973lr2HXE01lquPhSIXhj9EqVaiB76HbLmZwpWG51o4ICr3u CTRZHvgg/N+/A==
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:b241:6fff:fe09:a92b]) by tuna.sandelman.ca (Postfix) with ESMTP id 33C351800C; Sun, 15 Jun 2025 15:13:34 -0400 (EDT)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id D74871B8; Sun, 15 Jun 2025 15:13:15 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Paul Wouters <paul.wouters=40aiven.io@dmarc.ietf.org>
Subject: Re: Fully functional email address
In-Reply-To: <CAGL5yWb_4WOosEKym897xULKvk8wUn4xxmQE8xFeB=qtw1dSLg@mail.gmail.com>
References: <CAGL5yWaMixv5sEEMbRvTef8q4OzdjRYre7wA28VosTvQfGfq7Q@mail.gmail.com> <CAGL5yWZoSGxi0i3npwvpHHm0_oBm2DisXucGt0mQtvSTVKPKtw@mail.gmail.com> <6.2.5.6.2.20250615022053.0bb5fd18@elandnews.com> <CAGL5yWb_4WOosEKym897xULKvk8wUn4xxmQE8xFeB=qtw1dSLg@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sun, 15 Jun 2025 15:13:15 -0400
Message-ID: <18892.1750014795@obiwan.sandelman.ca>
Message-ID-Hash: 7YI55CL227C4WHNISBASKPDAXD3DTIUS
X-Message-ID-Hash: 7YI55CL227C4WHNISBASKPDAXD3DTIUS
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xpHr_dtRvu6MIBTa7EmbYI4GbkU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>


Paul Wouters <paul.wouters=40aiven.io@dmarc.ietf.org> wrote:
    > In this particular case, the individual should be aware, as they added
    > an auto-responder that senders need to respond to with a magic
    > incantation constituting some binding legal contract. They should not
    > be surprised that the majority of IETF participants will refuse to
    > engage with such additional terms.

    > I want to note that using the IETF mailing lists for off-topic
    > discussions because you cannot email people individually, is not a good
    > reason for using our mailing lists.

So, assume it's on-topic.
Assume it's a sectorial reviewer.
Assume some AD tells me that I'm supposed to respond to their review.

Now, would you mind if I just decline to interact?

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.34.0 | Report a Bug | By Email | System Status