[Sml] Re: Structured Email and AI Agents
John R Levine <johnl@taugh.com> Tue, 26 August 2025 00:52 UTC
Return-Path: <johnl@taugh.com>
X-Original-To: sml@mail2.ietf.org
Delivered-To: sml@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 5B8C458E4C4D for <sml@mail2.ietf.org>; Mon, 25 Aug 2025 17:52:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.401
X-Spam-Level:
X-Spam-Status: No, score=-4.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="LJmMWRNc"; dkim=pass (2048-bit key) header.d=taugh.com header.b="eNR8eDmt"
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 7bLH4WpnZQWW for <sml@mail2.ietf.org>; Mon, 25 Aug 2025 17:52:24 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B5C4F58E4C47 for <sml@ietf.org>; Mon, 25 Aug 2025 17:52:24 -0700 (PDT)
Received: (qmail 5135 invoked from network); 26 Aug 2025 00:52:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=140a68ad0548.k2508; t=1756169534; x=1756515134; bh=opcbLM/rUPPohzjdVhtKvs95hKglm0fdpiT/km8LGDc=; b=LJmMWRNcUFvud2K/S/3ELM5hvEpDDa1aj3QC76xxuiOn4PZ7MffgwmAixLse3PHhMMkTVYx1dF7I9oDMi0xnknVqpEVW8H9BbNSjXtfM1BWNztvdW9I3gpEXPRv2uF3lJS+JSIWx0T4Nz1iHkewI0LpdaVtHWuwTWxXw7m7NWUuxze9aOaWGG7JC5AbeXV2dXxh+E7dXF1wtcIWceSZI7Lvwjuqipf9jIBOsXcuLAvLow1ecH05P1L7qbsrwZybVI/zO1R5A8zA4Yc1qA8ZicH5p/PcIpdYossOgCXzVOGg8AmPqnzodVP4yfsPEDf4B9zCE8iijD8vZ88jTWD9V2A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=140a68ad0548.k2508; bh=opcbLM/rUPPohzjdVhtKvs95hKglm0fdpiT/km8LGDc=; b=eNR8eDmtcJWIimU/XOJsIaC2hNygwJe7vlmxb362N+vnaNkVER0F5wnB3vD8zSSmj/79ow/7xjJL/TEtSf8Jg2cRa2npLBCcOmWcPNeZMBYw9FKOom/UGpdUjddExP4AUZ92DlkakpJJHltk+WvkruyiS6dwEJ/o36lymFaeHnNEdIlbMPrsAEBYP+tFfwGpQqKGTxz+SaGNm2hJMrVrxczirFqXEIBTSbc9JbHHVkAsqStxIX5dDM8YK9yDwks3KJVdN++Z1qSQv5az5DiI+gEr0TrJVzRIXb8n7BTmqB9eOieMBTK0fDxbKCiEsePGKG1hziukNDcfvDUJO3kK9A==
Received: from ary.qy ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 26 Aug 2025 00:52:23 -0000
Received: by ary.qy (Postfix, from userid 501) id 4AEC6D9738C2; Mon, 25 Aug 2025 20:52:23 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 0443BD9738A4; Mon, 25 Aug 2025 20:52:23 -0400 (EDT)
Date: Mon, 25 Aug 2025 20:52:22 -0400
Message-ID: <6ea763c2-925a-3f3f-9d52-a357256e55b7@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Adam Sobieski <adamsobieski@hotmail.com>, "sml@ietf.org" <sml@ietf.org>
In-Reply-To: <DS4PPF69F41B22E0E98B3B664276E8FFA9EC53EA@DS4PPF69F41B22E.NAMP223.PROD.OUTLOOK.COM>
References: <DS4PPF69F41B22E72C08B1885D3E7B1571DC53EA@DS4PPF69F41B22E.NAMP223.PROD.OUTLOOK.COM> <20250825192803.1CE42D96C6E8@ary.qy> <DS4PPF69F41B22E0E98B3B664276E8FFA9EC53EA@DS4PPF69F41B22E.NAMP223.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: ROTHHDXXR6MGU72ODUZSK5OH3SSNNMYC
X-Message-ID-Hash: ROTHHDXXR6MGU72ODUZSK5OH3SSNNMYC
X-MailFrom: johnl@taugh.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; 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: [Sml] Re: Structured Email and AI Agents
List-Id: Structured Email <sml.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/V7p4N9mbspmketpKhMfW2rOfwQE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sml>
List-Help: <mailto:sml-request@ietf.org?subject=help>
List-Owner: <mailto:sml-owner@ietf.org>
List-Post: <mailto:sml@ietf.org>
List-Subscribe: <mailto:sml-join@ietf.org>
List-Unsubscribe: <mailto:sml-leave@ietf.org>
On Mon, 26 Aug 2025, Adam Sobieski wrote: > One example scenario for wanting to be able to contact an end-user's AI agent via email would be to request information about how to communicate with the AI agent using another protocol. "My end-user wants to schedule a meeting with members of a work team, your end-user is in the list of contacts, I propose we consult our calendar data to find alternatives, dates and times to present to our end-users. How do I coordinate with you using A2A?" Sure, my agent sends the mail to you, your agent sees it, replies, and files it in the "Already Handled" folder. > As considered, for email addresses shared between end-users and their AI > agents, end-users wouldn't tend to want to receive notification chimes > when their AI agents received email messages, but they would tend to > want to continue to receive such notification chimes for those email > messages intended for them instead. Similarly, end-users would tend to > want special folders for their AI agents' messages to be automatically > sorted into. If the agent can't sort the mail and tell your mail program to skip the notifications for mail it's already handled, I'd look for a better agent and/or mail program. If you need special stuff in the message to tell the recipient MTA how to handle it, that's not AI or an agent, that's just ordinary mail sorting which we do today. R's, John > P.S.: Moments ago, while exploring Sieve's RFC's [1], I found mention of > a "+" syntax in RFC 5233 ( https://www.rfc-editor.org/rfc/rfc5233 ) It's entirely up to the mailbox owner if they want to use subaddresses and what syntax they use. The plus sign is a somewhat common convention but it is not universal. Some systems use other characters for subaddresses, some don't have subaddresses at all. As that RFC says: NOTE: Because the encoding of detailed addresses are site and/or implementation specific, using the subaddress extension on foreign addresses (such as the envelope "from" address or originator header fields) may lead to inconsistent or incorrect results.
- [Sml] Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents John Levine
- [Sml] Re: Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents John R Levine
- [Sml] Re: Structured Email and AI Agents Michael Richardson
- [Sml] Re: Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents Michael Richardson
- [Sml] Re: Structured Email and AI Agents John Levine
- [Sml] Re: Structured Email and AI Agents Ben Bucksch
- [Sml] Re: Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents John R Levine
- [Sml] Re: Structured Email and AI Agents Michael Richardson
- [Sml] Re: Structured Email and AI Agents Steffen Nurpmeso
- [Sml] Re: Structured Email and AI Agents John Levine
- [Sml] Re: Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents Adam Sobieski
- [Sml] Re: Structured Email and AI Agents Arnt Gulbrandsen
- [Sml] Re: Structured Email and AI Agents Michael Richardson
- [Sml] Re: Structured Email and AI Agents Michael Richardson