🚀 go-pugleaf

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

>Dan, output from --debug isn't very clear, so I would appreciate any 
>help I can get with this.

This looks like a suitable time to get a cup of coffee...

>So, here follows the output of "slrnpull --debug".  Everything looks fine apart
>from the message ID of the last body the server tries to send, which looks
>corrupted. The corrupted message body (or message ID) seems to prompt slrnpull
>to reply with a 'QUIT' command. Whether this causes the connection to drop, or
>occurs as a result of it, I don't know.

Well, sending QUIT is a very effective way to tell the news server that
you've finished: the issue being why this is being sent.

><200 news.demon.co.uk NewsBorg [nnrp-01]
>>MODE READER
That's needed by some INN configurations, most "reader" software sends
it just in case.
><200 news.demon.co.uk NewsBorg [nnrp-01]
>>XHDR
><501 command syntax error

That's slightly odd: XHDR without parameters doesn't make sense.  I
suspect it's just trying to find out whether or not the command is
available (a 500 response code would be given for a completely invalid
command).  Anyway...

>>GROUP demon.test
><211 45 12464 12508 demon.test group selected
>>XHDR Message-Id 2510-

The available articles are 12464 to 12508.  Quite why you're asking for
details starting at 2510 is "interesting".  Presumably slrnpull keeps
track of the article numbers somewhere and this data is, er, out of
date for some reason.  I'll check the code later, but it's unlikely to
be your real problem.

><221 Message-Id headers follow [12464-12508]
><12464 <M$pH2XAgHP65EAvY@crowfam.org.uk>
[...]
><12508 <m3g0lqx7lb.fsf@gonzo.localnet>
><.

That looks exactly as I'd expect.

>>head 12464
[...]
>head 12473
>>

This is presumably allowing for some sort of filtering.  The results
look fine initially...

><221 12464 <M$pH2XAgHP65EAvY@crowfam.org.uk> header follows
[...]
><221 12473 <slrn8up5jd.2ol.john@cartman.bungalow.bixter> header follows
[...]
><.

So far so good.  Now you want the bodies:

>>body 12464
[...]
>body 12473

This looks to be working correctly also.

><222 12464 <M$pH2XAgHP65EAvY@crowfam.org.uk> body follows
[...]

><222 12468 <m4tfs8.gmc.ln@p-joosten.demon.nl> body follows
><.

Now you start asking for some more headers, there's nothing inherently
wrong with that, though I'd expect the results not to appear until after
the body of 12473.

>>head 12474
[...]
>head 12483

><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.

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.

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?

Dan

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