Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!uakari.primate.wisc.edu!ames!ncar!mephisto!rutgers!netnews.upenn.edu!dsinc!cdin-1!ki4pv!tanner
From: tanner@ki4pv.UUCP (Dr. T. Andrews)
Newsgroups: comp.mail.elm
Subject: Re: A basic Wish List
Summary: editing headers
Message-ID: <00000QW@ki4pv.UUCP>
Date: 3 Mar 90 12:25:29 GMT
References: <1066@philmtl.philips.ca> <5644@ists.ists.ca> <6319@orca.wv.tek.com>
Reply-To: tanner@ki4pv.UUCP (Dr. T. Andrews)
Organization: CompuData Inc., DeLand
Lines: 24
X-Snail: 1409 E. New York Ave. / DeLand, FLA   32724
X-Phone: +1 904 736 0866

Two considerations seem to bother people.
	(1) we don't use elm as news reply agent because it can't cope
	    with headers in a file as is normally desired.
	(2) everyone hates the header-edit screen, which does not show
	    the headers to be added from "elmheaders

Solution to consider: have "elm" dump its headers into a file.
Include the "elmheaders" data.  When/if the headers are to be edited,
just call up the local editor, as is done for the body.  At message
transmit time, read the headers from the file to extract "To:",
"CC:", "BCC:".  Use that information.

The out-going message should contain a cleaned copy of the header
file, followed by a blank line and the body file.  Cleaning would
be the removal of obvious errors like blank lines and lines which
are neither continuations nor of the form "..*: ..*".  (Note that
this rule will eliminate blank header lines such as "CC:" to no one.)

Of course, once Elm uses a file and optionally the local editor for
its messages, it becomes nearly trivial to add a "-r" switch to tell
it that it's in send-only mode, and that it may immediately read
headers from a file whose name is the next argument.
-- 
...!{bikini.cis.ufl.edu allegra bpa uunet!cdin-1}!ki4pv!tanner