Fully functional email address

S Moonesamy <sm+ietf@elandsys.com> Sun, 15 June 2025 11:03 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 5F9723525559; Sun, 15 Jun 2025 04:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 1
X-Spam-Level: *
X-Spam-Status: No, score=1 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 VprcIUnaegg5; Sun, 15 Jun 2025 04:03:23 -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 5D6973525556; Sun, 15 Jun 2025 04:03:23 -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 55FB2oPs027981 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 15 Jun 2025 04:03:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1749985401; x=1750071801; i=@elandsys.com; bh=0I8OSvWrS6xAk5Vlg8q8h1WFa+hscGOmED6qFuZE/hw=; h=Date:To:From:Subject:In-Reply-To:References; b=Kw2X23r4RWLHSv7ei1N+VF+MbRc7rx6yRzF80XfvVCi5qPGIdF5Gs29344bnt3UDP M7pZ6/k/LkBteSA2fm9Kv6W6C/AxkdwjWxNB1lYr4oBYsyr41WwCkWKJJr8lEDshQV ZpnXJ4CfDsnfaOoHEUeD7kOhPMftKE0pQIWGOleA=
Message-Id: <6.2.5.6.2.20250615022053.0bb5fd18@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 15 Jun 2025 03:45:46 -0700
To: sec-ads@ietf.org, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Fully functional email address
In-Reply-To: <CAGL5yWZoSGxi0i3npwvpHHm0_oBm2DisXucGt0mQtvSTVKPKtw@mail.g mail.com>
References: <CAGL5yWaMixv5sEEMbRvTef8q4OzdjRYre7wA28VosTvQfGfq7Q@mail.gmail.com> <CAGL5yWZoSGxi0i3npwvpHHm0_oBm2DisXucGt0mQtvSTVKPKtw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: DCECLNI7YGT34GWOT4V7PBSNNGGXC2C4
X-Message-ID-Hash: DCECLNI7YGT34GWOT4V7PBSNNGGXC2C4
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/mLuQzc9aYPz0NpaExJMK0ZbiFow>
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>

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.

Regards,
S. Moonesamy