Re: [ietf-smtp] Make username optional in email addresses

John Levine <johnl@taugh.com> Sat, 18 February 2023 18:59 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28316C14F74A for <ietf-smtp@ietfa.amsl.com>; Sat, 18 Feb 2023 10:59:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.147
X-Spam-Level:
X-Spam-Status: No, score=-4.147 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="nvzPDvez"; dkim=pass (2048-bit key) header.d=taugh.com header.b="mBl4WowT"
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 ApQKxMIdg7pp for <ietf-smtp@ietfa.amsl.com>; Sat, 18 Feb 2023 10:59:49 -0800 (PST)
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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28D41C14F748 for <ietf-smtp@ietf.org>; Sat, 18 Feb 2023 10:59:48 -0800 (PST)
Received: (qmail 3689 invoked from network); 18 Feb 2023 18:59:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=e67.63f12023.k2302; bh=YjkVKn+Fv6CuWVTxxg2bAdvlUhSmRfcep9EJaWgMS10=; b=nvzPDvezcMi12TPmyG7/Up/gfZgviv4FsZvU6nQZjFn6I7BtDppUKuM2q4tI7CTkQKHChc/YxDu5Rh/Dd/pcl9gPqcQMGHHwtfIlSHeVSjAbUKYq8i/9Z8hm39eJza1KeE0Xa8a/x8NU3U6VoXm9dO8+D4M17D3X7/8661m/HTo8DMDhgcamINoqkiAKcgBe6BLh0VryoAi1IPp03hrNCTnfMCskTn6Ghf7+Drek+DSWKqJYZ0o9B7lFMa/pUmYGUUX38LOYA9PYWNjss9WE+g0Z7t6mgB0sHbDJs53W3Bgf2TC1LElVfZnk/CcDWMEu1Oszm1X6eEhUh7leSRf+eQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=e67.63f12023.k2302; bh=YjkVKn+Fv6CuWVTxxg2bAdvlUhSmRfcep9EJaWgMS10=; b=mBl4WowTnQP4B4C7Hlu7xdiFWxHg1BL0FvVZz3Qpl/RVU6lkYqJSBy6BwP8aTo9MUWNesenK/fd73+XXbmTmToerCUijyRkhxg5ne+JpU9s6huZG0XOsP6S8aJVRXky8Vr5k19DTi2+Y+KyoXSsBy5n9B/VgGW6AjVIzNl0jONkl5WoseyQOgyGI1WiTpKDmDcy72XX5md4p70tTZcbcM88lm1g1HI1ASwM6CDfJbVPue3cm4PNSz6Nee5fuSvJrLStw9QHNuA3+9HpmjsZxW1uLwsqfTH8NeqIVEGEEnrGnUgU3/xHIAhsAAvrqAvJJYfn/PC8OKNTNcbCF8LmkNQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 18 Feb 2023 18:59:47 -0000
Received: by ary.qy (Postfix, from userid 501) id 9CD8A99C86D3; Sat, 18 Feb 2023 13:59:45 -0500 (EST)
Date: Sat, 18 Feb 2023 13:59:45 -0500
Message-Id: <20230218185946.9CD8A99C86D3@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: scottantipa@gmail.com
In-Reply-To: <CAG6nNWfDhuAYyOyAFt-6eshBafWXRztnYwTfQfwi7YQaOSQo0A@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/3hpio7ZwT3bvy8IzNqlqYcWuleY>
Subject: Re: [ietf-smtp] Make username optional in email addresses
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2023 18:59:55 -0000

It appears that Scott Antipa  <scottantipa@gmail.com> said:
>I'm mostly curious to hear if folks think there could be sufficient demand
>for this, even if it takes years to build up that demand and eventually
>update the infrastructure. Its not a hair on fire problem, just what I
>think would be a very nice change.

Hi.  I've had personal domains since about 1992, which makes me a fairly
but not unusually old timer here.

I'm pretty sure the answer to your question is "no". As other people
have pointed out, there is a great deal of value in giving different
people different addresses in your domain, largely so you can tell who
leaks them to spammers and turn them off.  I have given out at least
a thousand in mine.

I also believe that although the number of people with personal
domains seems large in nerd circles, it's insignificant in the world
at large and I cannot imagine that large mail systems would be willing
to change their software for a change like the one you propose.

The suggestion of a role address like the ones in RFC 2142 is not a bad
idea.  Dunno if anyone's likely to adopt it, but it won't break anything
and doesn't demand software upgrades.

R's,
John

PS: Apropos of RFC 2142, uucp@computer.org is me.  Some addresses are in
practice more standard than others.