Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!gatech!seismo!mcvax!unido!hmm From: hmm@unido.UUCP Newsgroups: net.mail Subject: Re: Unreachable Machines Message-ID: <11500004@unido.UUCP> Date: Fri, 31-Jan-86 03:57:00 EST Article-I.D.: unido.11500004 Posted: Fri Jan 31 03:57:00 1986 Date-Received: Sun, 2-Feb-86 01:03:06 EST References: <1942@peora.UUCP> Sender: notes@unido.UUCP Lines: 22 Nf-ID: #R:peora:-194200:unido:11500004:000:1112 Nf-From: unido!hmm Jan 31 08:57:00 1986 I think the gateway at ucbvax is the culprit in this case. The gateway should transform a route in the routing language of one network into the equivalent rout in the other's network routing language. That is, a route "...!uucphost1!uucphost2!arpa-gateway!arpahost1!arpahost2!arpahost3!user" should look like "@arpahost1,@arpahost2: user@arpahost3" after the gateway. This is a valid rfc822 address and preserves the exact meaning of the uucp route. The fact that most mailers consider "user%host2@host1" equivalent to "host1!host2!user" does not make it a standard. However, please keep in mind that all this stuff applies to the envelope only. Mail headers should be in rfc822 format wherever possible to minimize user irritation. The bangs are just a means to get my message transported over the uucp network, I don't want to see them in my mail... Avoid @'s in uucp routes ! Avoid !'s in arpa addresses ! Let the gateways do the dirty work ! If the gateway is broken, fix it !!! Hans-Martin Mosner , One of the postmasters at unido University of Dortmund, Germany