Under what circumstances will LISTSERV create a new header before the
existing header when forwarding submissions to the editor?  I had never
encountered this behavior on several lists for which I am the primary
editor, but the editor of an Internet list (which I am redistributing)
complains that he gets double headers whenever a submission is sent to
one of the BITNET/EARN peers instead of the Internet list address.
 
Is it the case that his location behind a mail gateway is what makes
the difference?  I can see that LISTSERV could forward the mail file
to me along BITNET paths, bypassing mailers along the way and so not
caring what the mail header says, but has to make the mail deliverable
through the gateway.  I suppose it is then easier for LISTSERV to
construct a new header from scratch than to weave Resent- lines into
the existing header.  Is that it?
 
An example follows, in case one is needed.
 
--Mark
---------------------------example mail-------------------------------
>Return-Path: <[log in to unmask]>
>Received: from icsa.rice.edu by sumex-aim.stanford.edu (4.0/inc-1.0)
>	id AA20756; Thu, 23 Feb 89 09:58:46 PST
>Message-Id: <[log in to unmask]>
>Received: from ICSA.RICE.EDU by icsa.rice.edu (IBM VM SMTP R1.2) with BSMTP id
> 3641; Thu, 23 Feb 89 11:57:23 CST
>Received: by RICE (Mailer R2.01) id 3640; Thu, 23 Feb 89 11:57:20 CST
>Date:         Thu, 23 Feb 89 11:57:19 CST
>From: Revised List Processor (1.5o) <[log in to unmask]>
>Subject:      File: "INFO-MAC MAIL" being sent to you
>To: [log in to unmask]
>
>Received: from SYSB.UARK.EDU by ICSA.RICE.EDU (Mailer R2.01) with BSMTP id
> 3624; Thu, 23 Feb 89 11:56:25 CST
>Received: by UAFSYSB (Mailer R2.01) id 4197; Thu, 23 Feb 89 11:55:54 CST
>Date:         Thu, 23 Feb 89 11:46:26 CST
>From:         CB Lih <CL06076@UAFSYSB>
>Subject:      Developer Stack 1.2r
>To:           info-mac@rice