Re: BATV mangling email address

S Moonesamy <sm+ietf@elandsys.com> Wed, 16 September 2026 21:56 UTC

Received: from mx.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mx.ietf.org (Postfix) with ESMTP id 28F3031 for <ietf@ietf.org>; Wed, 16 Sep 2026 21:56:03 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=fail ("headers rsa verify failed") header.d=elandsys.com header.s=mail header.b=eLoqiXoW; 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.38.4]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 68GLtPZk029166 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Sep 2026 14:55:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1789595737; x=1789682137; i=@elandsys.com; bh=L/rbciYKi1djKDputrA2nIRbYyms+meHCZUtBAjdkQg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=eLoqiXoWDte+qLTFS/r51DJlVxjLJow+yGPNzC3Cb/ytbgLp4eBIaCRgGGE9F7UiU F/l1L6pjMDr6I4slLqi2hWTzh96stIihqU2iv7wVO/qfPI8YJTZLQ2HecWKs/kZqD0 xrANZGepFvVR1YEAZsEMnjlhJEiwEKcm/QuNX6is=
Message-Id: <6.2.5.6.2.20260916141000.08cddbe8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 16 Sep 2026 14:50:57 -0700
To: "Salz, Rich" <rsalz@akamai.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: BATV mangling email address
In-Reply-To: <CH2PR17MB40226B69DE979E739FA5CBC7CDB92@CH2PR17MB4022.nampr d17.prod.outlook.com>
References: <20260915063443.7D1255A@mx.ietf.org> <BY5PR04MB7059DCBD8AF8AFC5FCD45A15B9BA2@BY5PR04MB7059.namprd04.prod.outlook.com> <BY5PR04MB7059D9B7E45F0FCD40956D79B9B92@BY5PR04MB7059.namprd04.prod.outlook.com> <8b88be1d-ef45-4d5a-9dcb-cb7d67c95c7b@everything-ops.net> <BY5PR04MB7059434C925AF058F12EBDBDB9B92@BY5PR04MB7059.namprd04.prod.outlook.com> <6.2.5.6.2.20260916104250.14d15918@elandnews.com> <CH2PR17MB40226B69DE979E739FA5CBC7CDB92@CH2PR17MB4022.namprd17.prod.outlook.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: L5BOQKMGYPVK7CWULESA67CZJQJD7PJ4
X-Message-ID-Hash: L5BOQKMGYPVK7CWULESA67CZJQJD7PJ4
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/N1NMdzxWSFxivRetP6SBxO49ASk>
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 Rich,
At 01:08 PM 16-09-2026, Salz, Rich wrote:
>It also happens to me. "Salz, Rich 
>(rsalz@akamai.com)" is what MS Outlook shows when composing this message.

I first noticed the issue when I read an email 
which you sent to one of the mailing lists.   I 
assumed that it was another one of those changes for DMARC mitigation.

The reply from Bron Gondwana has the following:

   On Wed, Sep 16, 2026, at 16:08, [subscriber]@relay01.ietf.org wrote:

His mail user agent picked up an email address 
format which is similar to the one which my mail 
user agent would use in reply to a mailing list 
message.  It's probably the comma in the display 
name causing the rewrite to include two email 
addresses in the "From:" header field.  That's 
not compliant with RFC 5322, Section 3.6.2 (Page 
23) as there should also be a "Sender:" header field.

Regards,
S. Moonesamy