Re: Fully functional email address

Paul Wouters <paul@nohats.ca> Thu, 19 June 2025 23:30 UTC

Return-Path: <paul@nohats.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 73B32372689D for <ietf@mail2.ietf.org>; Thu, 19 Jun 2025 16:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.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 1WraMIplBhQF for <ietf@mail2.ietf.org>; Thu, 19 Jun 2025 16:30:45 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::85]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8BA3A3726892 for <ietf@ietf.org>; Thu, 19 Jun 2025 16:30:45 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4bNcKw05x3zDFX; Fri, 20 Jun 2025 01:30:44 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1750375844; bh=aFc+j30Ax1gSs7aYRIZcax4NLvQ3RBbH7lJKBbb/syo=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=N1n0A1VsG7ikykpjfUvP5WylUSoh/7ZL3PR5a+rqvIjoATnj/0iQCQ0zzH9fRzW0Q 1NcNfqiIfEn/VujJUz0jonl/4wiGn8hCaafgH1H0MHXCj8T2/EZMigtL13hGT7qXXf 2QoKgX8COA2LVmTmpkBJKs25f8/ncB/6kWKAK4EM=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id qLebDyq46TKP; Fri, 20 Jun 2025 01:30:42 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 20 Jun 2025 01:30:42 +0200 (CEST)
Received: from smtpclient.apple (bras-base-toroon01zb3-grc-70-184-146-216-109.dsl.bell.ca [184.146.216.109]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 9B57E15E7425; Thu, 19 Jun 2025 19:30:40 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-09D29B75-6FAC-489E-92DA-A6522CBD3567"
Content-Transfer-Encoding: 7bit
From: Paul Wouters <paul@nohats.ca>
Mime-Version: 1.0 (1.0)
Subject: Re: Fully functional email address
Date: Thu, 19 Jun 2025 19:30:22 -0400
Message-Id: <93C31BF9-61D6-452B-81B7-552D947EAC9D@nohats.ca>
References: <8cc02d64-9c6e-48aa-94bc-3dab4ed00f6c@cs.tcd.ie>
In-Reply-To: <8cc02d64-9c6e-48aa-94bc-3dab4ed00f6c@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: iPhone Mail (22F76)
Message-ID-Hash: ZLABZJKNP2CODJL6KLBWA2G6XIJMZR32
X-Message-ID-Hash: ZLABZJKNP2CODJL6KLBWA2G6XIJMZR32
X-MailFrom: paul@nohats.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: IETF general list <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/NuczwzvAEB1wrN0YDZSmVekkEgc>
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>

On Jun 16, 2025, at 16:11, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> 
> Hiya,
> 
> As far as the subject line goes: I think we ought be accommodating
> if we can and not try insist that a few people who make odd choices
> about email all have whatever we consider 'fully functioning email'
> (but that we haven't documented;-).

I disagree. If we tolerate it of a few people, we need to tolerate it from everyone and soon the ietf becomes a forum of autoresponders with ChatGPT challenges and fire hydrant puzzles talking to each other drowning out real contributions.

But in this case the auto responders adds legalese too:

I'm a rather primitive computer program, and I'm not sure whether your
message is bulk mail.

If you reply to this notice, you are (1) acknowledging that [recipient]
does not want to receive bulk mail; (2) confirming that your
message is not part of a bulk mailing; and (3) agreeing to pay [recipient]
$250 if your message is part of a bulk mailing.

When using my official dayjob email address, should I consult my company lawyer on this? If the cc: is an email list, is it bulk? Does mailman add a Bulk: header to the list copy they receive ?

There is also text in there that if the From: matches a certain email address than it is a forgery because the sender auto responder bot claims that address is not used for any mailing lists by its human, yet that’s exactly the email addresses that sent it to me, so if following this senders own autoresponder, I must treat their email as a forgery. Should I now make educational guesses as to whether which part of the auto responder is valid or ignorable ?

Offloading your spam problem to manual actions of others is wrong and it doesn’t scale for all of us. Therefore we should not tolerate it from anyone. 

Adding legal requirements on email distributions of IETF mailing lists violates RFC 2026 and its successor process documents.

> I know of a handful of IETF participants (maybe 4-5) who make useful
> contributions and where one has to jump through hoops to have an
> email conversation. I think that's fine.

So I respectfully disagree that I need to accommodate these demands. Making useful contributions is not a waiver for bad (and costly) behaviour.


> In the current case, where such a person is appealing WG/AD actions,
> then I think we should go even further to accommodate them, because
> that is the right thing to do.

Someone claiming that we MUST follow our rules via form and legalese that violates our rules seems a rather ironic situation.

Based on a combination of the above, I facilitated them by taking the effort to explain what minor changes they could do in a resubmitted email to conform to our process so I could process the appeal. Note that these minor changes did not include “must use a fully functional email address”, although I warned them that if the discussion would become deemed off topic, I would have no valid method to respond to their email offlist.

I will also note that this was the third appeal of this person in a very short time and that they appealed two AD decisions to the IESG and those two to the IAB, and all four appeals were denied. I would like to remind people of https://datatracker.ietf.org/doc/statement-iesg-on-appeals-of-iesg-and-area-director-actions-and-decisions-20071004/

“The IESG further wishes to highlight that the primary aim of the appeals mechanism set out there is to resolve conflicts and move the IETF as a whole towards consensus, and it urges all participants to approach them in that light”

Seeing the amount of effort spent by the Responsible ADs, the IESG and the IAB, I think we can ask such a person to avoid any ambiguity about Note Well by sending one more email to the Responsible AD, and that furthermore the community had already been immensely accommodating and we have seen little to no good will in return.

Paul