Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!cbosgd!mandrill!hal!ncoast!allbery
From: allbery@ncoast.UUCP (Brandon Allbery)
Newsgroups: comp.sources.bugs
Subject: Re: Mail User's Shell (MUSH) and/or SMAIL bug
Message-ID: <6889@ncoast.UUCP>
Date: 24 Dec 87 06:34:05 GMT
References: <266@fig.bbn.com>
Reply-To: allbery@ncoast.UUCP (Brandon Allbery)
Followup-To: comp.sources.bugs
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 38

As quoted from <266@fig.bbn.com> by rsalz@bbn.com (Rich Salz):
+---------------
| In comp.mail.misc (<6807@ncoast.UUCP>), allbery@ncoast.UUCP (Brandon Allbery) writes:
| >... RFC822 states that ',' is the separator between
| >addresses, spaces are basically ignored in RFC822 addresses...
| Huh?  According to pages 10-12 of the RFC spaces separate tokens.  If
| there is to be a space in an address, it must be in a quoted string.  In
| particular,
| 	    Full\ Name@Domain
|     is not legal and must be specified as:
| 	    "Full Name"@Domain
+---------------

From the "grammar" for message headers in RFC822:

"2.7.  #RULE:  LISTS

	"A construct `#' is defined, similar to `*', as follows:

			"<l>#<m>element

"indicating at least <l> and at most <m> elements, each separated by one or
more commas (`,')....

"4.1.  SYNTAX

"...destination = `To'		`:' 1#address
		/ `Resent-To'	`:' 1#address
		/ `cc'		`:' 1#address
		/ `Resent-cc'	`:' 1#address
		/ `bcc'		`:'  #address
		/ `Resent-bcc'	`:'  #address"

QED.
-- 
	      Brandon S. Allbery, Moderator of comp.sources.misc
 {hoptoad,harvard!necntc,cbosgd,sun!mandrill!hal,uunet!hnsurg3}!ncoast!allbery
     [This space reserved for future quotes and similar brain twisters.]