Re: potable e-mail, now Trying to do too much (was Re: the introduction problem, etc.)

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Fri, 20 May 2022 11:41 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5455C14F6EC for <ietf@ietfa.amsl.com>; Fri, 20 May 2022 04:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.754
X-Spam-Level:
X-Spam-Status: No, score=-3.754 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nbVebCo-THtl for <ietf@ietfa.amsl.com>; Fri, 20 May 2022 04:41:52 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 699E9C14F6E7 for <ietf@ietf.org>; Fri, 20 May 2022 04:41:50 -0700 (PDT)
Received: (qmail 21775 invoked from network); 20 May 2022 11:36:55 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 20 May 2022 11:36:55 -0000
Message-ID: <9a3432d7-2593-0d1d-631d-0e09ed1f1f91@necom830.hpcl.titech.ac.jp>
Date: Fri, 20 May 2022 20:41:48 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0
Subject: Re: potable e-mail, now Trying to do too much (was Re: the introduction problem, etc.)
Content-Language: en-US
To: ietf@ietf.org
References: <20220519164943.3DD824144C1C@ary.qy>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <20220519164943.3DD824144C1C@ary.qy>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1zbeJXEF3nPePJjK2iy7Nox7gLc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2022 11:41:56 -0000

John Levine wrote:

> Technically it would not be hard to add a per-mailbox DNS lookup to SMTP,
> ignoring the detail that no two mail systems agree what a mailbox is.

FYI, according to a non-standard rfc881:

    Mailbox Support

       The design of the domain servers provides two levels of support
       for mail.

       The first, called "agent binding", is that the right hand part of
       the typical mail box (Y in X@Y) can be mapped a host that will
       either accept the mail as the destination or accept the mail for
       forwarding.

       The second, called "mailbox binding", is to map the entire mailbox
       (X@Y) to a destination (this mechanism can also support some
       mailing list functions).

						Masataka Ohta