🚀 go-pugleaf

> Flames and corrections gratefully accepted.

Here goes...

If you want to source-route (that's specifying which machines are to
handle your message) mail on the Internet, words from the Powers that
Be (I know, I was there :-) mandate that one use

	user%something@domain

where "domain" is a fully qualified domain name (registered and all).
The suggestion that you could use "user@ahost@bhost" is bogus and is a
relic of the past.  Strange that someone still remembers...

You are not to use

	@domain:user@something

if "something" is not registered and so on, and if it is, it's silly,
since the "@domain:" in front is superfluous.  Furthermore, if you use
this form, it needs "<" and ">" around it:

	<@domain:user@something>

Now, since the original requestor appears to have this archaic uucp
protocol and nothing else, it doesn't really matter to him.  All the
rest of you out there, though...

Oh, yes, and this about "incoming mailpaths"...  If they don't work,
load your gun and shoot upstream.  A dead system is better than a
header-mangling, address-munging system.

[Erik]