Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id MAA22387; Wed, 3 Apr 1996 12:47:42 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.4); Wed, 3 Apr 1996 12:45:57 -0500 Received: from po10.andrew.cmu.edu (PO10.ANDREW.CMU.EDU [128.2.10.110]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id MAA22183; Wed, 3 Apr 1996 12:45:50 -0500 Received: (from postman@localhost) by po10.andrew.cmu.edu (8.7.5/8.7.1) id MAA00612 for drums@cs.utk.edu; Wed, 3 Apr 1996 12:45:40 -0500 Received: via switchmail; Wed, 3 Apr 1996 12:45:39 -0500 (EST) Received: from nifty.andrew.cmu.edu via qmail ID ; Wed, 3 Apr 1996 12:44:49 -0500 (EST) Received: via niftymail; Wed, 3 Apr 1996 12:44:49 -0500 (EST) Sender: Chris Newman Date: Wed, 3 Apr 1996 12:44:49 -0500 (EST) From: Chris Newman Subject: Re: generating RFC 822 addresses To: drums@cs.utk.edu In-Reply-To: <9604031446.AA01298@mercutio.admin.kth.se> References: <828416297.20873.0@nifty.andrew.cmu.edu> <19960402044725.9750.qmail@koobera.math.uic.edu> <9604031446.AA01298@mercutio.admin.kth.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <828553489.10043.0@nifty.andrew.cmu.edu> Olle Jarnefors writes: > I have found one use for providing real world name information > in _both_ the phrase part and a comment, as examplified by my > own > > From: Olle Jarnefors > (=?iso-8859-1?q?Olle_J=E4rnefors?=) This is certainly a reasonable thing to do with comments, and I see no reason to outlaw it. It should be simple to state a requirement for the "phrase " format (when the human name is known) over the "addr-spec" format without outlawing comments after the address. (continue) ----- Chris Newman , http://www.contrib.andrew.cmu.edu/~nifty/ U.S. Citizens: Ask your representatives to support S.1567 for Internet free speech, and S.1587/HR.3011 for a right to Internet privacy and encryption.