Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id WAA18573; Sat, 19 Aug 1995 22:52:29 -0400
X-Resent-To: drums@CS.UTK.EDU ; Sat, 19 Aug 1995 22:52:27 EDT
Errors-to: owner-drums@CS.UTK.EDU
Received: from CU.NIH.GOV by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id WAA18566; Sat, 19 Aug 1995 22:52:26 -0400
Message-Id: <199508200252.WAA18566@CS.UTK.EDU>
To: drums@CS.UTK.EDU
From: "Roger Fajman" <RAF@CU.NIH.GOV>
Date:     Sat, 19 Aug 1995  22:51:32 EDT
Subject:  Re:  'Reply-To'

> Note: Listserv has a personal switch, I believe it is called
> FULLHDR. If you set FULLHDR, then you get the original non-munged
> headers, if you reset FULLHDR, you get the munged version. That
> sounds like a good idea, every subscriber can choose whether
> s/he prefers the original or the munged set.

Actually, FULLBSMTP is preferable.  As of LISTSERV 1.8b, it's the
default (but controllable by the list owner and the individual
subscriber) and can be abbreviated as FULL.  It was made the default to
keep MIME headers from being stripped out.  But it does not affect the
processing of Reply-to.  Most LISTSERV lists use "list,respect", but
the list owner can change that.  It means to insert a Reply-to for the
list if none is present already, but to leave any Reply-to put in by
the sender alone.