Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!gatech!seismo!brl-tgr!tgr!jordan@ucb-arpa.ARPA
From: jordan@ucb-arpa.ARPA (Jordan Hayes)
Newsgroups: net.mail.headers
Subject: Re:  Quiz - Parse this From line
Message-ID: <854@brl-tgr.ARPA>
Date: Wed, 18-Dec-85 16:59:31 EST
Article-I.D.: brl-tgr.854
Posted: Wed Dec 18 16:59:31 1985
Date-Received: Sat, 21-Dec-85 06:13:07 EST
Sender: news@brl-tgr.ARPA
Lines: 37


	From: hpcnou!dat@hplabsd (Dave Taylor)

 >> From noscvax!@MIT-MC.ARPA:hpfcla!hpcnoe!veeger!hpcnou!dat@hplabsd

Simple.

If there's a leading '@', use source-routing. If not, look for
the right-most '@' ... so, send the return message to "hplabsd" ...

Ah, they say -- "but that's not the truth ..."

Humbug.

You can't parse it correctly unless you make some assumptions about
where that address showed up at. If it showed up at a dumb UUCP host
connected to noscvax, you may not have a problem returning it to
there and having noscvax send to mit-mc which would send to hplabsd
which would send to hpfcla!hpcnoe!veeger!hpcnou!dat ... *ugh* !!

However, if the site it came from recieved the message *via* uucp,
but is also an arpanet host (can you say "seismo" "ucbvax" "topaz"
"sdcsvax" "harvard" + a cast of thousands ...), you have a problem,
since it will try to do the "correct" thing I mentioned above about
sending it to hplabsd (BTW: how about your own return address, Dave?)

Such a silly question to ask ... the answer is clear: you can't parse
addresses with multiple (conflicting) syntaxes ... I thought we cleared
this question up a few years ago ... *sigh*

Now: how about the solution? As simple as the answer to Dave's
Question ... uucp needs to use 822 addresses if they expect to get
decent service when getting gatewayed into/out of the Arpanet.

They can do whatever they want between themselves, but when in Rome ...

/jordan