Just received this mail and thought I should warn you all.  There's
 some automatted service at Ohio State that is not getting along with
 Listserv.  I've had too many mail rejections today, so my reading of
 these headers may be wrong.  But I think that Ohio State is sending
 mail out with a From: address that cannot receive mail.  And the
 mail rejection that comes back doesn't seem to trigger Listserv's
 "ignore this junk" tests right away.  In fact, I don't know what
 stopped this loop.  I've appended "*"s to the raw headers in the
 following note and truncated the file.  It went on for hundreds of
 lines, all similar to the lines that end this note.
 
 -jj
 
----------------------------Original message----------------------------
The enclosed  mail file, found in  the LISTSERV reader and  shown under the
spoolid 1995 in the console log, has been identified as a possible delivery
error notice for the following reason: mail  origin seems to be a mailer or
mail-daemon.
 
------------------------ Message in error (397 lines) -------------------------
*Received: from OHSTVMA.ACS.OHIO-STATE.EDU by JHUVM.BITNET (Mailer R2.07) with
* BSMTP id 1994; Tue, 09 Jul 91 17:21:38 EST
*Received: from OHSTVMA by OHSTVMA.ACS.OHIO-STATE.EDU (Mailer R2.07) with BSMTP
* id 9064; Tue, 09 Jul 91 17:22:38 EDT
*Received: from top.magnus.acs.ohio-state.edu by OHSTVMA.ACS.OHIO-STATE.EDU (IBM
* VM SMTP R1.2.1MX) with TCP; Tue, 09 Jul 91 17:22:21 EDT
*Received: by top.magnus.acs.ohio-state.edu (5.61/3.910213)
*	id AA11558; Tue, 9 Jul 91 17:21:42 -0400
*Date: Tue, 9 Jul 91 17:21:42 -0400
*From: <[log in to unmask]>
*Message-Id: <[log in to unmask]>
*To: [log in to unmask]
*Subject: hpuxa service unavailable
 
Your mail message that you sent to a computer user on the HPUXA
computer cannot be delivered because the HPUXA computer has
been permanently retired.
 
However, Ohio State has two programs that will assist you in
reaching your party.
 
1.  osu.edu  (e-mail forwarding computer).  This computer is
    designed to take a real first, middle, and last name and look up
    the computer address for you and then to forward the mail to
    the user.
 
    Send e-mail to the full name of the user by using the
    underline to connect the first, middle, and last name.
 
         Example:
 
              to send a message:  [log in to unmask]
 
 
2.  WHOIS:  This is a directory of faculty, staff, and students at
     Ohio State. You may connect to the OSU WHOIS service by using
     conventional Internet procedure
 
	Example:
 
              to use the OSU WHOIS service telnet to: [log in to unmask]
 
3.  You may get help for either of the services above by sending mail
     to the service:
 
          a.  Get help information  about the osu.edu mail forwarding
          service by sending mail to "[log in to unmask]".  The only line
          in the message should read,  "SEND FUZZE.HLP".
 
          b.  For help with WHOIS, send e-mail to "[log in to unmask]".
          In the message area put only these words, "SEND WHOIS.HLP".
 
If you need any additional help in reaching your party please feel
free to send e-mail to [log in to unmask]
 
For your convenience we have attached your original mail message.
 
>Received: from ohstvma.ircc.ohio-state.edu by top.magnus.acs.ohio-state.edu
 (5.61/3.910213)
>	id AA11531; Tue, 9 Jul 91 17:21:30 -0400
>Message-Id: <[log in to unmask]>
>Received: from OHSTVMA.ACS.OHIO-STATE.EDU by OHSTVMA.ACS.OHIO-STATE.EDU (IBM VM
 SMTP R1.2.1MX) with BSMTP id 8870; Tue, 09 Jul 91 17:19:13 EDT
>Received: from JHUVM.BITNET by OHSTVMA.ACS.OHIO-STATE.EDU (Mailer R2.07) with
> BSMTP id 8866; Tue, 09 Jul 91 17:18:48 EDT
>Received: by JHUVM (Mailer R2.07) id 1893; Tue, 09 Jul 91 17:05:48 EST
>Date:         Tue, 9 Jul 1991 17:05:47 -0500
>From: Revised List Processor (1.7a)
 <[log in to unmask]>
>Subject:      Message
>To: [log in to unmask]
>
>You are not a registered NAD (Node Administrator) for node
>HPUXA.IRCC.OHIO-STATE.EDU.  The  NAD   for  this  node  is
>[log in to unmask]
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of
 [log in to unmask]
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of
 [log in to unmask]
>U
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of
 [log in to unmask]
>U
>>>> You are not authorized to act on behalf of
 [log in to unmask]
>>>> You are not authorized to act on behalf of
 [log in to unmask]
>>>> You are not authorized to act on behalf of
 [log in to unmask]
>>>> You are not authorized to act on behalf of
 [log in to unmask]
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of [log in to unmask]
>>>> You are not authorized to act on behalf of
 [log in to unmask]
>U
 
 (much more of the same deleted...)