Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site hou3c.UUCP Path: utzoo!watmath!clyde!burl!hou3c!Margolin@MIT-MULTICS.ARPA From: Margolin@MIT-MULTICS.ARPA (Barry Margolin) Newsgroups: net.mail.headers Subject: Re: Malformed headers Message-ID: <840501204450.711421@MIT-MULTICS.ARPA> Date: Tue, 1-May-84 16:44:00 EDT Article-I.D.: hou3c.531 Posted: Tue May 1 16:44:00 1984 Date-Received: Wed, 2-May-84 06:19:49 EDT Sender: ka@hou3c.UUCP (Kenneth Almquist) Lines: 29 To: Ron Natalie Cc: header-people@MIT-MC.ARPA In-Reply-To: Message of 1 May 84 16:10 EDT from "Ron Natalie" Date: 1 May 1984 16:10 edt From: Ron Natalie Subject: Re: Malformed headers But an address must have soething to the right of the "@" and must contain the "@" as well! -Ron Once a messagessed to foo@bar is received by bar it may convert the address into any internal form it pleases, which generally begins by removing the "@bar". After UCLA-LOCUS forwards the message to UCB-VAX it is no longer in an SMTP environment, so @'s are no longer needed. Perhaps the wording of the steps was misleading, and I was inferring something different from you. It says that the header in step 3 was the way the message was received by UCB-VAX. I interpreted that to mean that this was what the header looked like after UCB-VAX received and munged it. Anyway, we are arguing minor semantics. The point of the message is obvious: UUCP hosts are all expected to know a route to an Arpa gateway, so the explicit route (with !'s) only has to be specified for the part of the route after traversing the Arpanet. As I said in a previous message, this is not realistic. What is to stop hosta from thinking hostb is closer to the Arpanet and vice-versa, causing all Arpa mail from or thru either host to loop forever? barmar