🚀 go-pugleaf

In article <1424@uw-entropy.ms.washington.edu>, hubert@ms (Steve Hubert) writes:
>   $#ether  $@uucp-relay.domain  $:a!b!c!user
>   $#ether  $@uucp-relay.domain  $:a!b!c!user@uucp-relay.domain
>   $#ether  $@uucp-relay.domain  $:a!b!c!user<@uucp-relay.domain>
>   $#ether  $@uucp-relay.domain  $:b!c!user%a.UUCP@uucp-relay.domain
>   $#ether  $@uucp-relay.domain  $:user%c.UUCP%b.UUCP@a.UUCP
>   $#ether  $@uucp-relay.domain  $:user%c.UUCP%b.UUCP%a.UUCP@uucp-relay.domain

Well, the problem is that you don't know what the RELATIVE  address a!b!c!user
should be started with. Let's say that machine "a" is connected to uunet.
Then I would say the proper address is
	a!b!c!user<@uunet.uu.net>

[You should leave the <@ host> in the address determined by ruleset 0
because the mailer rulesets or ruleset 4 will remove the "<" and ">".]

But the problem is, you don't know which internet machine is "closest"
to machine a. Therefore the address a!b!c!user@uucp-relay.domain
might not be right. Now the machine uucp-relay may re-write
the address if it has the path-alias database. Or it may not.
As an example, a!b!c!user@sun.com only works if machine "a" is directly
connected to sun.com.


IMHO, I would suggest
   $#ether  $@uucp-relay.domain  $:b!c!user<@a.UUCP>
provided that the relay has a direct connection to machine a, or
it have the pathalias database and will re-route to machine a.

In either case, I suggest you talk to the administrator ot the relay machine
and ask for their advice. There are no hard rules, and some sites
may have a preference.

--
Bruce G. Barnett	<barnett@crdgw1.ge.com>  a.k.a. <barnett@[192.35.44.4]>
			uunet!crdgw1.ge.com!barnett barnett@crdgw1.UUCP