🚀 go-pugleaf

In article <8562@tut.cis.ohio-state.edu> karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste) writes:
>Uh-huh.  Right.  Look at the headers here before you.  Try to tell me
>where it came from, or where it was going, or how it tried to get
>there.  I have no idea...
>
[ mucho stuff trimmed ]
>From: MAILER-DAEMON@tut.cis.ohio-state.edu (Mail Delivery Subsystem)
>Subject: Returned mail: Host unknown
>Message-Id: <8803181618.AA21981@tut.cis.ohio-state.edu>
>To: <shan%mcf%mibte%fmsrl7.uucp%eecae.ee@mailrus.cc.umich.edu>
>
>   ----- Transcript of session follows -----
>550 <sei.cmu.%sei%PT.CS.CMU.EDU%rochester%bbn%mit-eddie%bloom-beacon@tut.cis.ohio-state.edu>... Host unknown
>
>   ----- Unsent message follows -----

My bet is that someone was mailing along the news path, a longish one
that it looked like
  mcf!mibte!fmsrl7!eecae.ee.msu.edu!(unknown)!mailrus.cc.umich.edu!
     tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!bbn!rochester!(something about CMU).

The sad part is that the path could have gone
  mcf!umix!host.cs.cmu.edu!person

and avoided all this troubles.

I don't know if the problem is at mailrus (might be, gotta check) or with
one of the CMU machines not forwarding stuff along beyond their local
domain, or confusion resulting from the eecae.ee name, or whatever.
With a path as pathological as the one presented, it's a wonder that anything
happened to it at all.

--Ed