🚀 go-pugleaf

In article <20070706.1526.70706045snz$@i-m-t.demon.co.uk>
           v$af$ppint@i-m-t.demon.co.uk "ppint. at IMT" writes:

>     - hi; in dipspc article, <1173163692snz@nospam.demon.co.uk>,
>            pete@nospam.demon.co.uk adumbrated, and avowed:
> [snip]
> >
> >Haven't yet exercised the progressive dropping of second-oldest 
> >references once the length gets to 998 bytes (+ CRLF = 1000), 
> >which is what I understand rfc2822 to mean,
> 
>         - recursively, as may be necessary/desirable; and allowing
>         room at least for that reply's message-id to be appended to
>         the references: header line by anyone following-up to it...
> 
>         (= "yes" :-) )

Still haven't found the opportunity to test the new code (which 
is so ugly it simply _has_ to work ;-) ) but maybe if we keep 
this thread going long enough...  The main problem to my testing 
of this new code is that I don't subscribe to busy newsgroups, 
and by the time that any thread would be long enough to exercise 
it, the thread would likely be so far off-topic that I wouldn't 
bother posting anyway...

> >but hey! it's going to work first time ;-)
> >
>         - *g*  - from the last three-four month's silence ensuing,
>         should we presume that it did?       (- [a])
> 
>         - love, ppint.
>           [please drop the "v" and change the "f" to a "v",
>                     to email a reply or a cc.]
> 
>                                          [a] - or that it didn't?

Still unproven, but I stand by my earlier optimism :-)

Pete

PS You seem to have lost the "protext" from your msg-ids?

PPS Seeing your .sig reminded me of one I saw a while back in 
demon.test:

| A glass, being topologically equivalent to a finite flat sheet, can be
| neither "full" nor "empty"; it may or may not have some beer balanced
| on it.

Made me chuckle anyway.
-- 
   demon.ip.support.pc is for discussion of IP-related issues
   using plain DOS software - See the Which Group FAQ:-
   ftp://ftp.demon.co.uk/pub/doc/general/whichgrp.faq