Re: Fully functional email address

Paul Wouters <paul.wouters@aiven.io> Sun, 15 June 2025 15:31 UTC

Return-Path: <paul.wouters@aiven.io>
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 B58D5353251A for <ietf@mail2.ietf.org>; Sun, 15 Jun 2025 08:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level:
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=aiven.io
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 2nboMgHbqSlw for <ietf@mail2.ietf.org>; Sun, 15 Jun 2025 08:31:51 -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 ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 44671353250C for <ietf@ietf.org>; Sun, 15 Jun 2025 08:31:51 -0700 (PDT)
Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-ad8a8da2376so601784666b.3 for <ietf@ietf.org>; Sun, 15 Jun 2025 08:31:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aiven.io; s=google; t=1750001510; x=1750606310; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=f9MvNNNEVJotQZUqyPFWVkmlfRVUORQUXsye5A/EENI=; b=GQTLdHM1fyd/Lk3pjig3d/Iwais/1W/0Khd0nJup9E2JwYjB3LGyCm8zWuBw1APx1h lIq0JkC/IjwYQyt6M8P3LoVqOoVR/O/Uq3LQ6jwoL2kcc1Wp6j1UkmT4P6rdZiCLVfk4 xFKuWX7p1T9zcxHLNwpABCYNU9Ns8iD7VE4wQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750001510; x=1750606310; 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=f9MvNNNEVJotQZUqyPFWVkmlfRVUORQUXsye5A/EENI=; b=Hr0Kct3UmH6akyXVwY1VitJgs1MKwDD2aL6roaFN3hNAn8wpwr0OaNM5Q3I0RgtGdx KnT/mAkq2hONKUO3tQi2JRPmfpqdXXrsYssHc3E0df2J9SELPmN4zLX8YIZgjeludYTf qBJ21ICS/yAyPOnYxsRfqo+E5FgddvQuaT7HSTVLWwIQel8MCZ7/Nv5tsRUEXJAX0Cgu 5pnufG2dxE5zWiXuKLzNjpxg5/rwBOiG6CiXCNFVXfachutQ4wcV2i4JzMHmhO8yy7qn xCG0T537vMLV/vv2jW1yOYuRRFLUIk1trAH8W8ogj/0/HBewpmbF0Csr1JXrZkqtri4H KyMw==
X-Gm-Message-State: AOJu0YyhbRC5F7f5GbOgBMw4GGQu4nq+yRf0t957g6B5avTHr4tzfaZy Wk3WOX+NGBbD09JhJEfG2/33PorxVaSj7CXvjjpkPYcsVQiJ7U2A4wKQbRx8ka7tKMMcZIyciwU 8xXJFjE22x0QVP0VK5pDN8JszswZqrrl9dlAePCdgg30jLxwDbMujb1o=
X-Gm-Gg: ASbGncueXnMzQXlupJuolH7nI5UlHVpIzZRhidB+IM0dlP/2Z0bLKNJeBDQJKp1h+/y FKtPsij+76Zu8q3drr0THGN4DDs3uhHDjaYEWEhEKhXaGCgaIY3tcSktNdswEoxj73wkEux/GQr ln0OuH+kRNOE8EJFPuGSeEb7Lu7k+FCej/VedSfgeZxljG/A==
X-Google-Smtp-Source: AGHT+IEbq2IHA4Sqa3phtJB4CHs2t3DNuwf8dE32660dFuP4y8kdOuz37pbHxJP1LWGCTc7Ib+Rc7asPZlrWMFOSwag=
X-Received: by 2002:a17:907:7f9f:b0:ade:4448:9a0a with SMTP id a640c23a62f3a-adfad34549bmr631640166b.19.1750001509758; Sun, 15 Jun 2025 08:31:49 -0700 (PDT)
MIME-Version: 1.0
References: <CAGL5yWaMixv5sEEMbRvTef8q4OzdjRYre7wA28VosTvQfGfq7Q@mail.gmail.com> <CAGL5yWZoSGxi0i3npwvpHHm0_oBm2DisXucGt0mQtvSTVKPKtw@mail.gmail.com> <6.2.5.6.2.20250615022053.0bb5fd18@elandnews.com>
In-Reply-To: <6.2.5.6.2.20250615022053.0bb5fd18@elandnews.com>
From: Paul Wouters <paul.wouters@aiven.io>
Date: Sun, 15 Jun 2025 11:31:38 -0400
X-Gm-Features: AX0GCFvUG_rswJ62g_belKOBH4bTp7oV9I9jCYJCc_35IZrswSXNwHdUaWoetRk
Message-ID: <CAGL5yWb_4WOosEKym897xULKvk8wUn4xxmQE8xFeB=qtw1dSLg@mail.gmail.com>
Subject: Re: Fully functional email address
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary="000000000000589f8e06379dfa91"
Message-ID-Hash: X4XH23QLII6UGYXZJ3BUZYYQ6LB35DZM
X-Message-ID-Hash: X4XH23QLII6UGYXZJ3BUZYYQ6LB35DZM
X-MailFrom: paul.wouters@aiven.io
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@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/ETdDTe6ngvXfEp0ya0b3lQE--Kk>
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 Sun, Jun 15, 2025 at 7:03 AM S Moonesamy <sm+ietf@elandsys.com> wrote:

> Dear Security Area Directors,
>
> I saw an email exchange about a complaint on the Transport Layer
> Security mailing list.  There was a request to "use a fully
> functional email address".
>
> One of the problems which became less infrequent over the years is
> email delivery issues when I reply to some participants by email.  I
> don't know whether those participants are aware that it was not
> possible to have an email reply delivered to them because their mail
> server rejected the email (reply).  I find it easier to copy a
> mailing list instead of getting in a discussion of whether the
> sender's or receiver's email address is fully functional or not.
>

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.

It seems you are talking about other mail connectivity issues. As Area
Director,
I myself have mostly stopped using the ietf aliases as these are not
reliable
enough anymore due to forced bad deployment of various anti-spam
technologies,
ironically devised by us at the IETF :P

Paul