Dotless domains

John Levine <johnl@taugh.com> Sun, 25 January 2009 00:14 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0P0EYfg026610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 24 Jan 2009 17:14:34 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n0P0EYtO026609; Sat, 24 Jan 2009 17:14:34 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0P0ELM2026602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-smtp@imc.org>; Sat, 24 Jan 2009 17:14:33 -0700 (MST) (envelope-from prvs=0269ed33c5=johnl@iecc.com)
Received: (qmail 71835 invoked from network); 25 Jan 2009 00:14:23 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 25 Jan 2009 00:14:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=k0901; i=johnl@user.iecc.com; bh=ubdb55+erPn/zFQR+zkK4Ht52O9sa+zY2zI0gK2AyA0=; b=Msjd5i+YTFN1CgWpjksU8eiaLBZ0MobGA2Ex1IRoeWqIydHAnMnNUwpd5crg5Yk2j27jvSz+J1JfqYj0q4vcn0CCPApf0Zp4e1QVhVg63Hwnh5qxCMte9R+yeU2EXrE7SzS4pCXES2WC3Y3r3uyEVfZi4thxgmY2wHSDk6aoCos=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=k0901; bh=ubdb55+erPn/zFQR+zkK4Ht52O9sa+zY2zI0gK2AyA0=; b=HQl2fSSTMMibem0ajodhvacN5L0DsNfTZzCombPcvEotJItl4wcU0LKSWG311YW8kjvWjTm6W1LZi5gjkv0qZAKQMa8IiBDVzcEU5UENpCHdQ78Rf40xRi1AUO9KdT2B2YI21jHYqdwLrvWPD40Vb7euw2XWIlOiDS9YK+Lc5AA=
Date: Sun, 25 Jan 2009 00:14:18 -0000
Message-ID: <20090125001418.76555.qmail@simone.iecc.com>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@imc.org
Subject: Dotless domains
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>

A friend* wonders about the SMTP treatment of addresses in TLDs.
Historically there have been a smattering of such addresses, most
famously n@ai, and there are 21 TLDs with MX records, but spot
checking shows that most appear to be config mistakes, with the MTAs
not actually accepting mail to postmaster@tld.

If ICANN does what they claim they're going to do and starts selling
thousands of new TLDs, we're likely to see a lot more dotless
addresses.  bob@aol, anyone?

As best I understand it, the prose description of addresses in 2821
allowed TLDs in addresses, but the ABNF didn't.  In 5321 the ABNF
changed to match the prose.  Although the DNS allows you to put a dot
at the end of a domain name to make it clear that it's an absolute
address, SMTP has never allowed that.

My impression is that in the real world, mail addressed to
postmaster@va is far more likely to be rewritten to
postmaster@va.example.com than delivered to the Vatican (which, as it
happens, will accept it.)  Mail addressed to postmater@va. with a dot
isn't valid under 821, 2821, or 5321, so some MTAs accept it, some
reject it.

Is the current situation with TLDs deliberate, or was the change in
5321 just aesthetic tidying up?  Is there any reason not to permit a
trailing dot in 5321-bis to bring it in line with DNS rules?

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Information Superhighwayman wanna-be, http://www.johnlevine.com, ex-Mayor
"More Wiener schnitzel, please", said Tom, revealingly.

* - no, really