Re: Fully functional email address

S Moonesamy <sm+ietf@elandsys.com> Sun, 15 June 2025 16:36 UTC

Return-Path: <sm@elandsys.com>
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 DA56A35351BE for <ietf@mail2.ietf.org>; Sun, 15 Jun 2025 09:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.3
X-Spam-Level:
X-Spam-Status: No, score=-0.3 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 6Zgep5fTR7TG for <ietf@mail2.ietf.org>; Sun, 15 Jun 2025 09:36:21 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id 28BF735351BB for <ietf@ietf.org>; Sun, 15 Jun 2025 09:36:21 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.114.30]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 55FGZfDv006260 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 15 Jun 2025 09:36:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1750005374; x=1750091774; i=@elandsys.com; bh=tMx/9QIOJaP7NOjRcaHETpwI8axdPcw8vtH5b+beQjo=; h=Date:To:From:Subject:In-Reply-To:References; b=umzojDteaXcc7Vy+CBrLMwVpBf+XkmphtTD6wUqf9i91NbkkpCEESYTz8DgiRWF43 fsVzjcEAQCaVTGk+uJ5+aeoqnUTpMq0ZOisqPHbuA/ah4wP0Y8U2ttw+27gmhYixN+ 0OWE9vli21YLQk/Zs9PTh3lFV6n1vqUtVCHxcd0A=
Message-Id: <6.2.5.6.2.20250615085447.0c801070@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 15 Jun 2025 09:34:45 -0700
To: Paul Wouters <paul.wouters@aiven.io>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Fully functional email address
In-Reply-To: <CAGL5yWb_4WOosEKym897xULKvk8wUn4xxmQE8xFeB=qtw1dSLg@mail.g mail.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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: 2GU2AJYRGPAHZOLPHQ4HGG3VSTFWZDKZ
X-Message-ID-Hash: 2GU2AJYRGPAHZOLPHQ4HGG3VSTFWZDKZ
X-MailFrom: sm@elandsys.com
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
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/4JuZwQXoNlfLJbtmU0sFxu5CYG0>
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 Paul,
At 08:31 AM 15-06-2025, Paul Wouters 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 don't use an auto-responder for communication as it can make 
communication quite complicated.  It would take some time to figure 
out where some binding contract might negatively impact me.  I don't 
do that at my location.  I am open to be convinced why it would be 
worthwhile to do that for some other location.

>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.

Yes.

>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

Yes (to the other mail connectivity issues).  One can do much about 
Bad Common Practice.

Regards,
S. Moonesamy