Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!ut-emx!linus!daffy!7thson
From: 7thson@daffy.slcs.slb.com (Chris Garrigues)
Newsgroups: comp.mail.headers
Subject: Re: RFC-822 'phrase' question
Message-ID: <399@linus.SLCS.SLB.COM>
Date: 23 Jun 89 19:57:14 GMT
References: <43c2245d.129dc@blue.engin.umich.edu> <1760002@hp-ses.SDE.HP.COM>
Sender: news@linus.SLCS.SLB.COM
Reply-To: 7thson@SLCS.SLB.COM (Chris Garrigues)
Organization: Schlumberger Lab for CS, Austin, TX
Lines: 44

In article <1760002@hp-ses.SDE.HP.COM> wunder@hp-ses.SDE.HP.COM (Walter Underwood) writes:
>> I have noticed that a number of mailers will generate From: lines like:
>>   From: John Q. Public <JQP@MIT-AI.ARPA>
>
>A safe version of this is:
>
>   From: (John Q. Public) JQP@MIT-AI.ARPA
>
>In strict 822-land, the angle brackets are only allowed if there is a
>route address, but the draft host requirements RFC amends the BNF to
>allow that.  The above example could have angle brackets, but they
>are not necessary.
>
>wunder

I don't see the problem with the other form.

Some of the rules from RFC822:
     authentic   =   "From"       ":"   mailbox  ; Single author
                 / ( "Sender"     ":"   mailbox  ; Actual submittor
                     "From"       ":" 1#mailbox) ; Multiple authors
                                                 ;  or not sender

 
     mailbox     =  addr-spec                    ; simple address
                 /  phrase route-addr            ; name & addr-spec
 
     route-addr  =  "<" [route] addr-spec ">"

     addr-spec   =  local-part "@" domain        ; global address

and a parse tree of the sample given above:
	From: John Q. Public <JPQ@MIT-AI.ARPA>	=>
	From: phrase <local-part@domain>	=>
	From: phrase <addr-spec>		=>
	From: phrase route-addr			=>
	From: mailbox				=>
	authentic


What's the problem?

Chris Garrigues,
7thSon@SLCS.SLB.COM