🚀 go-pugleaf

In article <817429693snx@holly.demon.co.uk>
   Mark Rogers <mcr@holly.demon.co.uk> writes:
> In article <4903ni$e40@gryphon.looking-glass.org>
>    bnb@gryphon.demon.co.uk (Brian Blackmore) writes:
> > Mark Rogers <mcr@holly.demon.co.uk> wrote:
> > >(...)
> > >Message-ID: <817087024snx@holly.demon.co.uk>
> > >References: <816201151snz@siberia.demon.co.uk>
> > > <816211836.5182@thokk.demon.co.uk> <816376122snz@alquds.demon.co.uk>
> > > <816389914snz@wash.demon.co.uk> <816696796snz@alquds.demon.co.uk>
> > > <816739142snz@wash.demon.co.uk
> > 
> > While we are talking about headers take a look at the references line that
> > cppnews has produced (I've wrapped it myself), in particular take a look
> > at the last message ID and you'll notice that its missing a '>'. Does the
> > author of cppnews know this, does anyone still maintain it, and can someone
> > please fix this (it messes threading up).

Yes, there is a problem with cppnews handling of long References lines. It
has some fixed length buffers, which can overflow.

It also has a problem in that it doesn't recognise split header lines on 
incoming news.

I do still maintain cppnews, when I have time. But I am currently very 
busy - in addition to my regular contract, I am doing some work on the 
"Virtual Access" product, from Ashmount Research, which is a combined 
Internet, CIX and Compuserve off-line reader. (Registered cppnews users can
get a discount on this product, by the way - "http://www.ashmount.com/va/"
for product details.)

As both of these jobs involve being paid a proper rate, they take
precedence over cppnews, the total income from which wouldn't pay for 1%
of the work involved :-( 

-- 
CPPNEWS news/mail reader for DIS. For details mail cppnews@trmphrst.demon.co.uk
trmphrst.demon.co.uk is NOT affiliated with ANY other sites at demon.co.uk.