Xref: utzoo comp.mail.uucp:2342 comp.mail.misc:1399
Path: utzoo!attcan!uunet!husc6!ukma!mailrus!ncar!tank!oddjob!matt
From: matt@oddjob.uchicago.edu (Matt Crawford)
Newsgroups: comp.mail.uucp,comp.mail.misc
Subject: Re: Another example why not to re-route
Message-ID: <913@tank.uchicago.edu>
Date: 25 Nov 88 17:02:30 GMT
References: <140@minya.UUCP>
Sender: news@tank.uchicago.edu
Reply-To: matt@oddjob.uchicago.edu (Matt Crawford)
Followup-To: comp.mail.uucp
Organization: If you worked here you'd go home by now
Lines: 19
In-reply-to: jc@minya.UUCP (John Chambers)

Here's my opinion on uucp path-munching, which may be no better than
anyone else's opinion.

If pass-through mail has a fully-qualified domain name in the
destination bang path, as

	rutgers!mimsy.umd.edu!elsewhere!eddie.mit.edu!somewhere!user

has, then the mailer takes shortcut to the rightmost fully-qualified
name.  Otherwise it either delivers to the first node on the path, if it
is a neighbor, or bounces it if it is not.

To the return-path on outgoing mail, I prepend "oddjob!" if there already
is a fully-qualified name in the path or "oddjob!oddjob.uchicago.edu!"
if there isn't.

This seems to work quite well.

			Matt