Path: utzoo!attcan!uunet!husc6!bloom-beacon!gatech!psuvax1!psuhcx!wcf
From: wcf@psuhcx.psu.edu (Bill Fenner)
Newsgroups: news.admin
Subject: Re: References line (RFC1036)
Message-ID: <1222@psuhcx.psu.edu>
Date: 12 May 89 14:50:50 GMT
References: <62.246A2DCC@jsheese.FIDONET.ORG>
Reply-To: wcf@psuhcx (Bill Fenner)
Organization: Engineering Computer Lab, Penn State University
Lines: 29

In article <62.246A2DCC@jsheese.FIDONET.ORG> jeffery@jsheese.FIDONET.ORG (Jeff Sheese) writes:
|However, the editor I use has the capability of putting message lines at the  
|header of every message.  It's completely user configurable, and the source  
|code is available for personal modification.
|
|Now the kicker.  When I export an FTSC message from MSGED to usenet using  
|UFGATE, the headers are automatically added.  Everything else is considered  
|the body of the message, therefore a blank line is added between the header  
|lines added from UFGATE.  Anything I add at the top of the message appears  
|after this blank line.
|
|If RFC1036 were changed to relax the restriction of all the header lines  
|appearing before the blank line, I could be compatible by configuring my  
|editor to place these lines in there automatically.

That would take quite a lot of changing on most of USENET's part.  Maybe
a better thing would be to ask the UFGATE folks to allow misc. header lines
that are at the top of the article to pass through in the header.  How
do you tell a header line from something like
First: I don't ...
or whatever?  I don't know.  Maybe keep a list of all the ones allowed
by RFC1036, or something.

  Bill
-- 
   Bitnet: wcf@psuhcx.bitnet     Bill Fenner       | "Yesterday starts
  Internet: wcf@hcx.psu.edu                        |  tomorrow; tomorrow
 UUCP: {gatech,rutgers}!psuvax1!psuhcx!wcf         |  starts today"
Fido: Sysop at 1:129/87 (814/238 9633) \hogbbs!wcf |       -- Marillion