Path: utzoo!utgpu!cunews!micor!ecicrl!clewis
From: clewis@ferret.ocunix.on.ca (Chris Lewis)
Newsgroups: news.software.b
Subject: Re: LET'S NAME THE GUILTY POSTING SOFTWARE!!!
Message-ID: <2202@ecicrl.ocunix.on.ca>
Date: 21 Jun 91 02:37:05 GMT
References: <2857E736.3519@tct.com> <1991Jun15.194129.25394@vlsi.polymtl.ca> <285E730F.4EC0@tct.com> <6068@gazette.bcm.tmc.edu> <1991Jun19.154645.11885@zoo.toronto.edu>
Organization: Elegant Communications Inc., Ottawa, Canada
Lines: 20

In article <1991Jun19.154645.11885@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes:
>In article <6068@gazette.bcm.tmc.edu> sob@tmc.edu (Stan Barber) writes:
>>Unfortunately, some news transports spool posted articles for later
>>processing by the posting software. In this case, the poster may not 
>>know the article had invalid header lines.

>I'd be curious to know what transport systems do this.

Bnews does.  If you invoke inews whilst expire is running, or have
turned on SPOOLINEWS (I think it's called that), the article will
be left in $SPOOLDIR/.rnews until a subsequent "rnews -U" or during
the rnews that expire fires up.  However, header checking is done
before the article is spooled, tho, there's obviously classes of
errors that the later rnews run could find that cause the article to be
rejected.
-- 
Chris Lewis, Phone: (613) 832-0541, Domain: clewis@ferret.ocunix.on.ca
UUCP: ...!cunews!latour!ecicrl!clewis; Ferret Mailing List:
ferret-request@eci386; Psroff (not Adobe Transcript) enquiries:
psroff-request@eci386 or Canada 416-832-0541.  Psroff 3.0 in c.s.u soon!