Newsgroups: news.software.b
Path: utzoo!henry
From: henry@zoo.toronto.edu (Henry Spencer)
Subject: Re: Sliding mail around inews
Message-ID: <1990Nov23.210131.2078@zoo.toronto.edu>
Organization: U of Toronto Zoology
References: <NELSON.90Nov22105755@image.clarkson.edu>
Date: Fri, 23 Nov 90 21:01:31 GMT

In article <NELSON.90Nov22105755@image.clarkson.edu> nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) writes:
>So, I've modified the contributed 'usenet' script so run 'rnews' instead
>of 'inews'.  This makes the rash assumption that the incoming mail is
>already properly formed.  In most cases it will be.  After all, since
>'usenet' adds the Newsgroups: and Path: header, what's left to be wrong?

Could be a moderated newsgroup.  Could lack a message-ID.  Several other
possibilities.  Inews checks for a lot of things.  The main consequence
of going via rnews rather than inews is that ill-formed news simply vanishes
into the bit bucket, rather than being reported.

>Also, along the same lines, I'm tempted to modify 'inews' so that it
>doesn't run relaynews immediately, but instead runs 'newsspool' so
>that relaynews gets run later...

The main problem with this is on sites that don't run newsrun during
busy times of the day.  Users tend to get restive if their posting
*seems* to just disappear into the void, even if it really is queued
up to be dealt with eventually.
-- 
"I'm not sure it's possible            | Henry Spencer at U of Toronto Zoology
to explain how X works."               |  henry@zoo.toronto.edu   utzoo!henry
