🚀 go-pugleaf

In article <828492008snx@holly.demon.co.uk>
	   mcr@holly.demon.co.uk "Mark Rogers" writes:

> Not sure where this should be posted, but I'd hope that someone suitable
> would at least see it here. I'm not at this point sure whether KA9Q is at
> fault, or the article itself.
>
> The full article follows, including the #!rnews lines from batch.txt:
>
>  -----8<-------8<-------8<-------8<-------8<-------8<-------8<-------8<-----
> #! rnews 0000017765
> Path: news.demon.co.uk!dispatch.news.demon.net!demon!mail2news.demon.co.uk!
> genial.demon.co.uk
> From: fred@genial.demon.co.uk
> Newsgroups: demon.tech.pc
> Subject: Enhanced IDE cards disable Modem
> Date: Tue, 02 Apr 1996 12:50:21 GMT
> Organization: A rare commodity
> Lines: 27
> Message-ID: <828362025snz@genial.demon.co.uk>
> Reply-To: fred@genial.demon.co.uk
> X-NNTP-Posting-Host: genial.demon.co.uk
> X-Broken-Date: Tues 02 Apr 96 12:33:45 GMT
> X-Newsreader: Demon Internet Simple News v1.30
> X-Mail2News-Path: genial.demon.co.uk
>

[article + blank line(s) snipped]

>
> #! rnews 0000001575
>  -----8<-------8<-------8<-------8<-------8<-------8<-------8<-------8<-----
>
> I would guess that the "." is the cause of the problem? (KA9Q thinks its
> found the end of the article?) Note that the blank lines above are very
> long (well in excess of 80 chars). I would be interested to know if the
> are actually in the article at Demon, or have been added by KA9Q.
>
> The news server I used (from nos.log) was 158.152.254.254.
>
> Mark.
> --
> int MeaningOfLife (void) { return 42; }   // mcr@holly.demon.co.uk
> function MeaningOfLife :integer; begin MeaningOfLife := 6 * 9 end;
> #! rnews 0000001929
> Path: news.demon.co.uk!dispatch.news.demon.net!demon!thokk.demon.co.uk!malcolm
> From: malcolm@demon.net (Malcolm Muir)
> Newsgroups: demon.ip.developers
> Subject: Re: DIS always adds newsbase\00000000.*
> Date: Tue, 02 Apr 1996 22:54:52 GMT
> Organization: Demon Internet Ltd.
> Lines: 30
> Message-ID: <828485692.18145@thokk.demon.co.uk>
> References: <828408131snx@holly.demon.co.uk> <828391088.4778@thokk.demon.co.uk> <828491642snx@holly.demon.co.uk>
> Reply-To: Malcolm@demon.net
> NNTP-Posting-Host: thokk.demon.co.uk
> X-NNTP-Posting-Host: thokk.demon.co.uk
> X-Newsreader: TIN [version 1.2 PL2]
>
> Mark Rogers (mcr@holly.demon.co.uk) wrote:
> > In article <828391088.4778@thokk.demon.co.uk>
> >    malcolm@demon.net (Malcolm Muir) writes:
> > > Mark Rogers (mcr@holly.demon.co.uk) wrote:
> > >
> > > > I noticed today that DIS (or is it ADDGROUP?) always adds the newsbase
> > > > file 00000000 and its accociated index file. Regardless of whether ACTIVE
> > > > actually defines this group (I have junk assigned to the filename "junk"
> > > > instead).
> > >
> > > If you have altered the code to call '00000000' junk, then you should
> > > also alter the code that checks for the presence of '00000000' to
> > > check for junk instead :)
>
> The "code" to call '00000000' junk is ~\spool\news\ACTIVE, and I have
> > indeed changed this. My point is that Addgroup is not looking at ALIAS,
> > but making assumptions which it perhaps should not. Addgroup certainly
> > has access to ALIAS in order to do its job, after all.
>
> What is ALIAS ? It is not to my recollection part of Snews ?
>
> The newsgroup name of '0000000' for junk is built into Snews and the
> support utilities. There is no support for any form of newsgroup file
> name other than the 8 digit numeric format.
>
> --
> Malcolm S. Muir				Demon Internet Ltd.
> Sunderland					322 Regents Park Road
> England					London N3 2QQ
>
>

I really don't know what's going on here, except that SNEWS seems
to be getting confused - possibly by the ".", possibly by the long
lines of spaces ( > 1000 chars, possibly > 2000 - haven't checked
exact layout).

Of interest is the appending of Malcolm's reply to a different
thread; this article does not appear in my list (wrong count?).
More peculiarly this second article was not included in my initial
attempt at this follow up after saying Y to the 'Quote article?' -
I had to write the original whole message out to a temp file in
order to requote it.

It looks as though fred was standing on the spacebar (resting his
copy of Dispatches on the kb while reading it?), the upshot of
which was to create a problem for UNBATCH.  If it is a buffer
size problem, it seems benign.	Will take a look this evening.
--
Pete