🚀 go-pugleaf

A mailing-list posting without an RFC-1036-conformant headers will be
disposed of the first up-to-date C-News site it hits.  The failures
I see are mostly due to bad message-ids, and specifically message
ids with spaces in them or bad domain-names.  (I attribute this to
the difficulty of getting some mail software - sendmail in particular -
set up right, and making sure it's shipped with a working .cf).

These are NOT legal message-ids:

<joe doakes@ysub>  (unquoted spaces)
<joe@ ysub.ysu.edu > (One of the .cf's shipped with NeXT 2.1 did this,
   		     leaving spaces around the hostname)
<big.long.message-id.without-an-at> (no '@')
<920310.184155.xyzzy@.ysu.edu> (bad domain-name)
<12345@ysu.edu.> (same)

Some sites running older news software versions can't handle message-ids
with unquoted spaces at all, I had to trap them in nntpxmit (and the
Unix nntpxmit does the same thing).  They can otherwise hang the news
transfer up.

Another example, this time user-created:

Subject: this is a very long subject line that is supposed to be
continued on the next line but the author didn't put a tab or space
at the beginning of the line.

The problem with this is that the header is continued, without white
space (tab or quote) at the beginning of continuation lines.

For more information, watch postings in news.admin about rejected
postings.  I'll start saving posts for a "hit-list" of offenders
to post here.  The RIGHT solution is to get people to fix their
software.  The WRONG solution is to fix their headers for them.

Doug
-- 
Doug Sewell, Tech Support, Computer Center, Youngstown State University
doug@cc.ysu.edu	   doug@ysub.bitnet	<internet>!cc.ysu.edu!doug
We've had 4 years of domestic policy failure.  Fire Bush this November.