Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site decwrl.UUCP
Path: utzoo!linus!decvax!decwrl!daemon
From: daemon@decwrl.UUCP
Newsgroups: net.mail
Subject: Message-ID, Destination is correct, if done right...
Message-ID: <4711@decwrl.UUCP>
Date: Tue, 27-Dec-83 22:36:48 EST
Article-I.D.: decwrl.4711
Posted: Tue Dec 27 22:36:48 1983
Date-Received: Wed, 28-Dec-83 06:09:38 EST
Sender: daemon@decwrl.UUCP
Organization: DEC Western Research Lab, Los Altos, CA
Lines: 15

From: John Covert <castor::covert>
That's right, that will prevent loops, as long as what is being
checked is the "current" destination, and not the original one.
 
Improperly implemented (for example, looking at the original
destination) this would also prevent someone from forwarding
a message to a destination which requires that the message
cross a path it has crossed before.
 
And the checking mechanism must also take into account the
fact that nodenames in different domains can have the same
name (apollo.uucp and apollo.enet are two different destinations).
 
/John
...{ucbvax,decvax,allegra}!decwrl!rhea!castor!covert