Email changes (was: change all subscriptions email address)

S Moonesamy <sm+ietf@elandsys.com> Mon, 21 September 2026 13:51 UTC

Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mx.ietf.org (Postfix) with ESMTP id AB26331 for <ietf@ietf.org>; Mon, 21 Sep 2026 13:51:45 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=fail ("headers rsa verify failed") header.d=elandsys.com header.s=mail header.b=kURXSvXF; dmarc=none; spf=pass (mx.ietf.org: domain of sm@elandsys.com designates 2001:470:f329:1::1 as permitted sender) smtp.mailfrom=sm@elandsys.com
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.80.55]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 68LDpWuD025718 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Sep 2026 06:51:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1789998703; x=1790085103; i=@elandsys.com; bh=SqSDrSY9GVKsDabjT1pZQtYT0Pm5Tidln9Vc6gD2P1Q=; h=Date:To:From:Subject:In-Reply-To:References; b=kURXSvXFmx8QpxDYn6X1MiwnNRh5DKy4lGCslW0bf0OJ4509p2KwWMgfPhS5KbLab df239xnXxSrgin2Eqr3k9R0skBMCVvPJWAeGYgL33CskEhEoCPNJW2mfE4wFvKecXy pSBUnw396DZ/uLgETVmlm6UmOUrpzGtihdxFbQQg=
Message-Id: <6.2.5.6.2.20260921051057.10214678@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 21 Sep 2026 06:50:55 -0700
To: jordi.palet@theipv6company.com, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Email changes (was: change all subscriptions email address)
In-Reply-To: <43132441-BE2E-47BF-83E5-0BB7991A8F7B@theipv6company.com>
References: <43132441-BE2E-47BF-83E5-0BB7991A8F7B@theipv6company.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Spam-Level: ***
X-Spamd-Bar: +++
Message-ID-Hash: AI25CWKPXLG2M4UNYLMWSQNJKL7GZG2L
X-Message-ID-Hash: AI25CWKPXLG2M4UNYLMWSQNJKL7GZG2L
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ietf.ietf.org-0; header-match-ietf.ietf.org-1; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
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/Nta88s4X8z84UeVREtq3ATIPhTE>
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>

Hi Jordi, All,
At 03:27 AM 21-09-2026, jordi.palet@theipv6company.com wrote:
>Not sure if this belongs here, but probably someone can help.
>
>I'm having troubles sending my emails to IETF 
>mailing list since the new system was in place.
>
>I've received multiple confirmation requests, 
>and after each one (for each email I sent), it 
>worked and my emails were processed.
>
>However, today, this systems don't like my 
>emails anymore, and I didn't got the 
>confirmation request, and the emails were not sent …

I tried subscribing to one of the mailing 
lists.  The instructions which I received by 
email from the GNU Mailman server said that I 
must first confirm that this is my email 
address.  I was also informed how to do that (by 
replying to the email).  I replied and included 
the confirmation token.  I received the following 
response by email: "Confirmation token did not match".

I am familiar with how to automate a confirmation 
[1].  I don't do it.  I am subscribed to other 
mailing lists.  Some of those mailing list use 
GNU mailman.  I have not encountered a similar 
issue subscribing to those mailing lists or to 
IETF mailing lists before the latest email changes.  I see two options:

   (a) There is something wrong with my email reply.

   (b) The relay01.ietf.org configuration for GNU mailman is not
       a standard configuration.

The email issue reported by Jordi is not entirely 
similar to the one I explained above.  Those 
email issues started happening after the latest 
changes to the email infrastructure.  The unusual 
part in the email issues is that email works but 
there can be an intermittent issue.  The 
consequence is that I have to think again whether 
it is worth the trouble to subscribe to an IETF 
mailing list or to send a comment/review.

The mailing list subscriber would not be 
receiving emails from a mailing list if he/she 
has to send a confirmation request to be able to 
send an email to the mailing list.  I assumed 
that the subscription email address is the same as the poster's email address.

The IETF used to disclose the list of subscribers 
previously.  I didn't see any notification about 
that change.  There wasn't much anonymity unless 
the subscriber used an anonymous or free email 
service.  The effect of the latest email changes 
is that there could be a minor loss of 
anonymity.  There was a discussion on the topic 
of anonymity to access the meeting WiFi.  I don't 
know whether anonymity was considered before the 
latest email changes were implemented.

Regards,
S. Moonesamy

1. I sent an email to tools-discuss@ to explain how it can be done.