🚀 go-pugleaf

	From: gds@sri-spam.ARPA (Greg Skinner)

	noscvax!hplabsd.arpa!....!hpcnou!dat

	Note I left MIT-MC out of the picture.  MIT-MC just
	redistributed the message -- it did not originate it, and has
	no right to be included in reply text.  I suspect possible
	munging of From or From: lines.  However, if you insist on
	seeing MIT-MC in there,

	noscvax!mc.mit.lcs.edu!hplabs.arpa!....!hpcnou!dat

Gregbo,

You clearly have shown your parsing skills, but I think what is missing
from this little point you made is the assumption that just because
noscvax is on the Internet that it will know about the hp site (by the
way, the original said "hplabsd" and you have "hplabsd.arpa" which does
not exist ... "hplabsd" is a nick-name for "hplabs.arpa" -- no "d" in
the .arpa-ized form. This is because the people running sendmail on
that machine have the local name go out on mail, instead of the
official name ... *sigh*)

Anyways, what i wanted to say was that the reference to mit-mc was in
fact necessary, and should indeed be included, unless you are
absolutely sure you can get to the hp site by yourself. When an
exploder is doing its work, it definately should put itself in the address.

What if I on a machine "foo" that is on a local ether with mit-mc send
to the list that redistributes to someone on a machine one UUCP hop
away from noscvax ... should the return be noscvax!foo!jordan ...? or
should it be noscvax!mit-mc.arpa!foo!jordan ...?

Although it certainly may be true that noscvax could theoretically have
an entry for foo in its /etc/hosts file (nosc, as you recall, is on
MILNET and does not need to have resolvers running yet ...) and *could*
make the smtp connection to foo itself, it should go back to mit-mc.

Manual editing of headers from list exploders is a mail wizards hobby.
Not for the children at home ...

/jordan