RE: history of using a comment for display-name?

"Larry Osterman" <larryo@Exchange.Microsoft.com> Tue, 13 March 2001 04:58 UTC

Received: from cs.utk.edu (cs.utk.edu [160.36.56.56]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA00916 for <drums-archive@odin.ietf.org>; Mon, 12 Mar 2001 23:58:51 -0500 (EST)
Received: from localhost (daemon@localhost) by cs.utk.edu with SMTP (cf v2.9s-UTK) id XAA15315; Mon, 12 Mar 2001 23:56:55 -0500 (EST)
Received: by cs.utk.edu (bulk_mailer v1.13); Mon, 12 Mar 2001 23:56:28 -0500
Received: by cs.utk.edu (cf v2.9s-UTK) id XAA15278; Mon, 12 Mar 2001 23:56:28 -0500 (EST)
Received: from df-inet1.exchange.microsoft.com (marvin@localhost) by cs.utk.edu with ESMTP (cf v2.9s-UTK) id XAA15261; Mon, 12 Mar 2001 23:56:25 -0500 (EST)
Received: from df-inet1.exchange.microsoft.com (131.107.8.8 -> df-inet1.exchange.microsoft.com) by cs.utk.edu (smtpshim v1.0); Mon, 12 Mar 2001 23:56:25 -0500
Received: from df-virus2.platinum.corp.microsoft.com ([172.30.236.33]) by df-inet1.exchange.microsoft.com with Microsoft SMTPSVC(5.0.2195.2831); Mon, 12 Mar 2001 20:57:11 -0800
Received: from 172.30.236.11 by df-virus2.platinum.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 12 Mar 2001 20:57:12 -0800 (Pacific Standard Time)
Received: from df-goofy.platinum.corp.microsoft.com ([172.30.236.130]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2831); Mon, 12 Mar 2001 20:57:12 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.4663.0
content-class: urn:content-classes:message
Subject: RE: history of using a comment for display-name?
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Mon, 12 Mar 2001 20:57:12 -0800
Message-ID: <52E28A515344104299B5E7AABC32045FD5036D@df-goofy.dogfood>
Thread-Topic: history of using a comment for display-name?
Thread-Index: AcCrFw/JH6b/ElfkQHi9IpWviKZENgAYXxag
From: "Larry Osterman" <larryo@Exchange.Microsoft.com>
To: "Keith Moore" <moore@cs.utk.edu>, "Maynard Kang" <maynard@pobox.org.sg>
Cc: <drums@cs.utk.edu>
X-OriginalArrivalTime: 13 Mar 2001 04:57:12.0779 (UTC) FILETIME=[111C21B0:01C0AB7A]
List-Unsubscribe: <mailto:drums-request@cs.utk.edu?Subject=unsubscribe>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id XAA00916

And then there's my old friend (used by a popular client at one point)

From: Foo@domain (Return Reciept Requested)

And if anyone cares (and probably nobody does), this is why Microsoft
Exchange explicitly ignores the "names in comments" convention - Before
we shipped Exchange 4.0 we promoted the comment field to the "phrase"
(if none was given) but one of our customers was using the
"RRR-in-a-comment" client, so we pulled the functionality).


-----Original Message-----
From: Keith Moore [mailto:moore@cs.utk.edu]
Sent: Monday, March 12, 2001 8:39 AM
To: Maynard Kang
Cc: Keith Moore; drums@cs.utk.edu
Subject: Re: history of using a comment for display-name? 


> I guess as a developer of e-mail software I find it mildly irritating
that
> I've always had to write code to support both the "phrase route-addr"
and
> "addr-spec (comments)" formats in e-mail headers. You can imagine the
> problem getting worse when dealing with non-ASCII in headers.. 

I have had the same irritation for mail software that I write
(even though it's not for public consumption, at least not yet)
I try to find a name in either the phrase or a following comment, 
and naturally I decode encoded-words.  I also try to deal with
extra quotes, untagged 8-bit characters (guessing whether they're
utf8, iso-2022-*, or something else), and phrases which are
entirely redundant with the address.

(so I translate each of the following:

"foo" <foo@domain> 
"'foo'" <foo@domain>
"foo@domain" <foo@domain>
"'foo@domain'" <foo@domain>

to simply 

<foo@domain>

it's a major pain, but the resulting display is a lot easier to read)

Most mail client these days seem to generate phrase rather than comment,

but this doesn't help someone writing a new mail reader.  Mail readers
may have to deal with messages that are decades old, so they end up 
needing to understand old conventions long after they are no longer 
generated.  

Keith