IETF Logo Mail Archive

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

John Levine <johnl@taugh.com> Fri, 24 February 2023 14:50 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 7A118C14E511 for <ietf-smtp@ietfa.amsl.com>; Fri, 24 Feb 2023 06:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.847
X-Spam-Level:
X-Spam-Status: No, score=-6.847 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_HI=-5, 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="FXoktlza"; dkim=pass (2048-bit key) header.d=taugh.com header.b="YseB5tJS"
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 Gj_OI6y52RWG for <ietf-smtp@ietfa.amsl.com>; Fri, 24 Feb 2023 06:50:51 -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 67D0CC14F6EC for <ietf-smtp@ietf.org>; Fri, 24 Feb 2023 06:50:46 -0800 (PST)
Received: (qmail 23329 invoked from network); 24 Feb 2023 14:50:43 -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=5b1c.63f8cec3.k2302; bh=ZBB72COqlKu/8ZvE2J9Gh5YcSUukA8EAXZztz9isrBk=; b=FXoktlzauXB11DYea2D8DagBaIBtPNcnFqkVzw3aggRpKkjSBkZr2dp6A24AXwPHQr8v7fG8hz9TW26SYJvvJ6JCc2ybEX1YuexkuI+p0xZpKRUCy7ZMJm63nno/ULMMBaJGum8DWK8CRBzU5b/CW5gkw4LQhykO2IsTzuG6hPKNe7kr/t3diiMK8h3RLBVmq+8R38NPwIQMCf1B5iRFxJfmt0If51eRLIDCExXtWKE3laV91kn5MxQKqYLL8DCMAcvo0KAARZA0RsDRI0BtiedgSoDtpomiryX6UNZx2xSUNxdoT0a/aHZDXXMqcI/ckPVFppTwL3c//Js8P3VycA==
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=5b1c.63f8cec3.k2302; bh=ZBB72COqlKu/8ZvE2J9Gh5YcSUukA8EAXZztz9isrBk=; b=YseB5tJSfA25LAZb5n8XDUYPWBh4p8SvqPdGXCU4TwTtfbcaZA1Zmh1gmzLLKmzfQDmjR/pS1PbElNTbeIsp9zvzD+tOOFebVBt01QRT5QZBK8+tCfouNuoeJ2b01Ve3NrGS3hOLBT4+lXnZqev2YuchMPKTi9gXb4TY++pKRJg+XSZ08CP3j4hKDp+WphDoU39rqH7Ekouj2+3jDZooKH1dztqDTL9mDGntGLLZfj7j/iHXb7AeJRN871mqf/PldR17f9psIRAzRXIbRSeRX49JunxKkRj3LdDbg25+F6sHZL78jBvzzesx6gpK2VEIF5uQVczoa2CvN0FMNlCO2g==
Received: from ary.local ([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; 24 Feb 2023 14:50:43 -0000
Received: by ary.local (Postfix, from userid 501) id 6B237A0BA401; Fri, 24 Feb 2023 06:50:40 -0800 (PST)
Date: Fri, 24 Feb 2023 06:50:40 -0800
Message-Id: <20230224145041.6B237A0BA401@ary.local>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: paul@pscs.co.uk
In-Reply-To: <1866188dd88.2923.9bfe8bcc586ac955e423c0e3d5444448@pscs.co.uk>
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/SsV1p3At-C1C_5TTyllWyOW3zUQ>
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: Fri, 24 Feb 2023 14:50:57 -0000

It appears that Paul Smith  <paul@pscs.co.uk> said:
>-=-=-=-=-=-
>
>Why not just have a specific email address which means that.
>
>In the same way that Web browsers will "autocomplete" a URL of 
>"example.com" to "https://www.example.com", a compliant email client could 
>"autocomplete" an email address of "example.com" to "something@example.com"
>
>The "something" could be fixed, or discovered via DNS or similar

I am having trouble understanding why it would be a good idea to add a UI feature
that is at most a minor convenience to the 0.0001% of mail users with vanity domains,
and baffling and wrong for everyone else.

R's.
John

v2.23.0 | Report a Bug | By Email