Path: utzoo!attcan!uunet!lll-winken!netsys!jsheese!jeffery From: jeffery@jsheese.FIDONET.ORG (Jeff Sheese) Newsgroups: news.admin Subject: Re: References line (RFC1036) Message-ID: <71.246B9252@jsheese.FIDONET.ORG> Date: 13 May 89 02:25:36 GMT Organization: JStek Enterprises - Frederick, MD Lines: 39 References: <1222@psuhcx.psu.edu> In an article of <12 May 89 14:50:50 GMT>, wcf@psuhcx.psu.edu (Bill Fenner) writes: >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. I'd have to refer back to RFC1036, but maybe those misc header lines have no more than one or two words followed by a colon. Then the s/w can ignore anything past the blank line that follows. How can the s/w tell the difference between a valid misc header line and 'First: I don't...' in the first line of the message? Well as we say in Fidonet, RTFD and 'Caveat Emptor'. I'll request the source for NEWSOUT just to see if I can make the necessary adjustments. At least it will give me a starting point for the software necessary to make myself compatible. OBTW - I entered a sample References line to the first line in the body of this message. I'd like to request a few people to test it's validity with their news software. Please respond via mail *only* if it works and I'll summarize. If it doesn't work then don't respond. In the meantime I'll examine the source for the PC implementation of SED to see if I can convince it NOT to put cr/lf pairs in it's output files. Maybe that would be a quick kludge. -- Jeff Sheese - via FidoNet node 1:109/116 UUCP: ...!netsys!jsheese!jeffery ARPA: jeffery@jsheese.FIDONET.ORG (I am sole owner. My opinions represent my company.) (Send all flames to null@jsheese.Fidonet.ORG)