IETF Logo Mail Archive

[dispatch] Re: DISPATCH guidance requested / Per-send sender ident ity verification for SMTP submission (SENDAUTH)

S Moonesamy <sm+ietf@elandsys.com> Thu, 03 September 2026 08:00 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: dispatch@mail2.ietf.org
Delivered-To: dispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3652B13499C04 for <dispatch@mail2.ietf.org>; Thu, 3 Sep 2026 01:00:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1788422446; bh=MKdpn/nA1tuarKYICAvcZARp7mXx+1nMpkdh2DRx1IM=; h=Date:To:From:Subject:In-Reply-To:References; b=V9aH9PeN/IhXSA83SLiPz9ofp3a2D1DxxuKPTwWfsOop5gaMwyXvnSskRSl8wKwP3 067J8dFNmGOukPCZiRcFL76yQoyrGb+NvDQIMI/7fQg9To+T2/h0BoE68mJlhKppIn d9wVarYqcyzOj/Sqk0RUyVut5lkkC+v70tG+fj2M=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 aEJM0PRErXjh for <dispatch@mail2.ietf.org>; Thu, 3 Sep 2026 01:00:44 -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 94BD913499C01 for <dispatch@ietf.org>; Thu, 3 Sep 2026 01:00:44 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.225.114.25]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 6838045j029396 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Sep 2026 01:00:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1788422438; x=1788508838; i=@elandsys.com; bh=MKdpn/nA1tuarKYICAvcZARp7mXx+1nMpkdh2DRx1IM=; h=Date:To:From:Subject:In-Reply-To:References; b=sRhGJyfl1VgdX98BkJqV0tqNvAva/CMAN9rCnjE+83zK/d4FC6fL4NVPbrEWgWk0i J8gmtNl6XtUDnQB+IkHR5nU0wadG0LD1g0F0cqJZId4ZzBq477jSNpSnaRcDbSi8fF 59mb81onyYcrSDZ1IPwHFJd8ETioNosH6aL/fOTM=
Message-Id: <6.2.5.6.2.20260902234524.0b6aece0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 03 Sep 2026 00:57:50 -0700
To: cc15000@gmail.com, dispatch@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <CALYaMK+RmVjqzgzGaZt9NzcNOqnDxCmgdzD_asXx5G7uva3TWA@mail.g mail.com>
References: <CALYaMK+RmVjqzgzGaZt9NzcNOqnDxCmgdzD_asXx5G7uva3TWA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: IWKHNUQBHIFT4Y6R76BY3IPS4BY2SAZA
X-Message-ID-Hash: IWKHNUQBHIFT4Y6R76BY3IPS4BY2SAZA
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dispatch.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
Subject: [dispatch] Re: DISPATCH guidance requested / Per-send sender ident ity verification for SMTP submission (SENDAUTH)
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/y2pdW7qf-sKRSO1eaBOw-RKfrC4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Owner: <mailto:dispatch-owner@ietf.org>
List-Post: <mailto:dispatch@ietf.org>
List-Subscribe: <mailto:dispatch-join@ietf.org>
List-Unsubscribe: <mailto:dispatch-leave@ietf.org>

Hi Christopher,

Around the turn of the last century the (U.S.) Defense Information 
Systems Agency wrote a guide.  Some of the information in the guide 
(RFC 2360) remains useful.

The feedback which this working group is supposed to give is listed 
in the working group's Charter.  The following points may be relevant:

   (a) there are not enough individuals willing to complete the work 
in the IETF.

   (b) there is no interoperability concern.

   (c) no people interested in an interoperable solution.

I would have to have my identity verified each time I send an email 
according to the subjet line.  I might view that as a mere 
inconvenience.  Another person may view it as an annoyance. It could 
become an unhappy customer problem.

U.S. NIST SP 800-177 (Revision 1) discussed various email-related 
technologies.  I suggest reading the document as you mentioned a law 
in your initial message.

Regards,
S. Moonesamy

v2.46.0 | Report a Bug | By Email | System Status