🚀 go-pugleaf

In article <G2tz2r.oBu@dgsys.co.uk>, I wrote:
>In article <slrn8v4aip.5lq.chris@rael.demon.co.uk>, Chris Medcraft 
><chris@rael.demon.co.uk> wrote:

>><222 12469 <7poous4obqrhr5siij5j0pnufa5njiro9f@4ax.com> body follows
>><Bldfkjsdflkj
>>>QUIT

>I see. That *is* the body of article 12469, and should be perfectly
>valid.

>You still have articles up to 12508 for which I'd expect the HEAD/BODY
>commands before QUIT.  Also, slrnpull hasn't waited for the response to
>the commands still in the pipeline and a clean termination by the remote
>server, which seems a bit odd.

This is definitely the root of the problem.

>For what it's worth, that article isn't (any longer?) available from
>news.freeserve.net.  If the issue is just that slrnpull chokes on the
>content then that might explain why you don't have the problem with
>Freeserve.

Or it could be something else.

>Well, I've got slrn-0.9.6.2 here and will (a) do some tests and (b) look
>at the source to see if there's an obvious reason for it to fall over
>when presented with the data above.  This will require another cup of
>coffee or two.  In the meantime, please can you confirm which version of
>slrn(pull) you're using?

Just to confirm: with the slrnpull from 0.9.6.2 all works perfectly for
me.  Looking at your headers I can make a guess as to the version you're
using, I'll see if I can find a copy and try that instead.

Other things which might have a bearing are your slrnpull.conf and maybe
the header files when your version was built.  Does the slrnpull log
file give any further clues?

Dan

-- 
Dan Glover (dan@dangl.demon.co.uk)