[Emailcore] Re: [Last-Call] Re: Re: Re: Your (Roman's) DISCUSS on draft-ietf-emailcore-as and status of the document

S Moonesamy <sm+ietf@elandsys.com> Fri, 25 September 2026 11:08 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 5B1D230 for <emailcore@ietf.org>; Fri, 25 Sep 2026 11:08:09 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=fail ("headers rsa verify failed") header.d=elandsys.com header.s=mail header.b=Br2KtO8G; 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.82.247]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 68PB7K0B011947 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Sep 2026 04:07:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1790334471; x=1790420871; i=@elandsys.com; bh=YA4y4v+MW0ch/bMRwpFCW3JV4ak0SS3YRFi09K0udSg=; h=Date:To:From:Subject:In-Reply-To:References; b=Br2KtO8Gm0xTV3gX2kXIU3R89vQHiBk4OPapdhAmFYcKyI4Za+ej70MNkmS0y2xUU ZKiqobkCizP1ktVC4nsJNoAd0t7BrFC8GN5pJcLDae5N+RgPS4VlqfH69gAGKe5DVa JASF9CDWhQ4xl8SSQ6Vtl/9TdJDgENmh9O9dToWI=
Message-Id: <6.2.5.6.2.20260925024023.0ae50998@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 25 Sep 2026 04:05:09 -0700
To: Ted Lemon <mellon@fugue.com>, emailcore@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <dbc035ff-a4e5-4d2b-a91b-e4fc995eae69@app.fastmail.com>
References: <716c75ca-c302-4c8e-85e4-6a151c1be249@app.beta.fastmail.com> <CALtcm6RYTctn96RZ7v0fpYAyKOY7fJa+OsZEkYY6ApczyuPYUg@mail.gmail.com> <CAChr6Sz+yRaC1cH0LEiRkV5V=mcXmEVeHT4Ff3QakowqmhZx3A@mail.gmail.com> <8d7840b5-0e2d-4d57-98e5-af12e93787f2@lear.ch> <CAL02cgRsWNy4RJ+xokdy3EOHGPYqP6nC1AX_dEnOvA5KXQiTCA@mail.gmail.com> <e4dccdcb-b450-4c38-9548-d4b3e66d71dc@lear.ch> <DM4PR11MB5469AEDF89A4E0CB9FFBF7EDB5822@DM4PR11MB5469.namprd11.prod.outlook.com> <CAChr6SxmXz86Uec2mcaKhVaJAnktsX2M82nFaOtQWDkO8B7b7w@mail.gmail.com> <CH2PR17MB4022DFB345DC70AE8AC3B2E8CD822@CH2PR17MB4022.namprd17.prod.outlook.com> <arSrUojV6EAxyhlp@chardros.imrryr.org> <57f5b5ce-0d19-4976-bba0-351b59989af8@huitema.net> <3757d6c6-5b82-9182-3b50-163a522fb40e@ietf.email> <139BC44B9F223591EA1C1B31@PSB> <216BFDF8-0F06-4F96-8A51-493ACA40A7B8@fugue.com> <CAH48Zfx1W7qt+xqgP2fqC+aqP_2z2RgVUT=vxU1c2_NNWW90oQ@mail.gmail.com> <dbc035ff-a4e5-4d2b-a91b-e4fc995eae69@app.fastmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Level: ***
X-Spamd-Bar: +++
Message-ID-Hash: ZY2DLMMOBXBBEZ2MVWQYXZXLYGXBFX5A
X-Message-ID-Hash: ZY2DLMMOBXBBEZ2MVWQYXZXLYGXBFX5A
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; 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
Subject: [Emailcore] Re: [Last-Call] Re: Re: Re: Your (Roman's) DISCUSS on draft-ietf-emailcore-as and status of the document
List-Id: EMAILCORE proposed working group list <emailcore.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/Wn8QRRH1Bjxn94SfgYR-sBowGic>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emailcore>
List-Help: <mailto:emailcore-request@ietf.org?subject=help>
List-Owner: <mailto:emailcore-owner@ietf.org>
List-Post: <mailto:emailcore@ietf.org>
List-Subscribe: <mailto:emailcore-join@ietf.org>
List-Unsubscribe: <mailto:emailcore-leave@ietf.org>

Hi Ted,

[Cc trimmed]

At 04:10 PM 24-09-2026, Ted Lemon wrote:
>My concern is not for the privacy of corporate email.

The scenario which you gave was for mail between two sites, Fastmail 
and IETF.  The headers in one of your emails show that x25519 was 
used for the key exchange and ECDSA P-256 was used as the server 
signature.  mx.ietf.org injected information in the headers stating 
that DKIM and SPF checks were successful.  As a quick reply, I'd say 
that everything looks okay.

You mentioned privacy in the comment.  I'll view it as what people 
out there say when they mention that word.  The email could have been 
sent securely but it is not necessarily private.  There is some 
filtering which occurs between sender and receiver.  You would be 
receiving too many offers about products which you need if the mail 
traffic was unfiltered.  There are reporting loops where information 
from the email is shared.  My guess is that some of that happened.  I 
would have to take a closer look to say whether it could be a concern or not.

Regards,
S. Moonesamy