Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!ames!elroy!usc!skat.usc.edu!blarson
From: blarson@skat.usc.edu (Bob Larson)
Newsgroups: comp.mail.uucp
Subject: Re: Domain Registration (was Re: rewriting FROM: lines)
Message-ID: <17512@usc.edu>
Date: 30 May 89 04:55:57 GMT
References: <8577@chinet.chi.il.us> <3135@sun.soe.clarkson.edu>
Sender: news@usc.edu
Reply-To: blarson@skat.usc.edu (Bob Larson)
Distribution: na
Organization: USC AIS, Los Angeles
Lines: 22

In article <3135@sun.soe.clarkson.edu> ahd@sun.soe!clutx.clarkson.edu writes:
>	@a:@x.y.z:you@b

Why can't the self-proclaimed rfc822 experts read and remember rfc822
style routing?

The correct route is:

	foobar <@a,@x.y.z:you@b>

foobar may be any legal comment, and if you want to follow the host
requirments draft (ietf-hosts.rfc on venera.isi.edu) rather than
rfc822, it may be omited.  (I don't know of any mailer that actually
requires it.) The angle brackets are definitly required.  Some hosts
require that all hosts listed (a, x.y.z, and b) be known domains, but
I consider this a rather pedantic enforcement of rfc822 rules.

-- 
Bob Larson	Arpa:	blarson@skat.usc.edu
Uucp: {uunet,cit-vax}!usc!skat!blarson
Prime mailing list:	info-prime-request%ais1@ecla.usc.edu
			usc!ais1!info-prime-request