Incomprehensible news server response

[Steve Holden]

Here's some debug output from a program in which I use a next() followed by
a head() on an nntplib.NNTP object. I cannot understand why the server
response differs between the two. Is this allowed by the standards (doesn't
look like it from my reading of RFC997), or should I be complaining to my
news server host?

Of the three articles I've included, 82599 and 82600 look crazy, 82601 looks
as I would expect. Any light shed on this matter would be most welcome.

regards
 Steve

*cmd* 'NEXT'
*resp* '223 82599 <3AA45A66.8A4B07F9 at mindspring.com>'
*cmd* 'HEAD 82599'
*resp* '221 82599 Mon, 05 Mar 2001 19:32:54 -0800'
l_hill at mindspring.com wrote 82599
*cmd* 'NEXT'
*resp* '223 82600 <GdZo6.24467$1D5.1007863 at e420r-atl1.usenetserver.com>'
*cmd* 'HEAD 82600'
*resp* '221 82600 Mon, 5 Mar 2001 22:52:20 -0500'
*** I wrote 82600
*cmd* 'NEXT'
*resp* '223 82601 <mailman.983850427.23541.python-list at python.org>'
*cmd* 'HEAD 82601'
*resp* '221 82601 <mailman.983850427.23541.python-list at python.org>'
m.wilson at bibliocraft.com wrote 82601