it seems that i've found another bug in JAMNNTPd... this time it is in the   
   XOVER response... according to the RFC, there are a number of fields that   
   XOVER should return... JAMNNTPd returns all of them /except/ the last two,   
   bytes and lines... according to the spec, if data is not available for a field   
   in the response, a null field is sent... in this case two tab characters side   
   by side... JAMNNTPd only outputs one pair of tab characters which fills the   
   bytes field but the lines field is not handled... the fix is to add another   
   "\t" to the command_xover routine...   
      
   in nntpserv.c, find the line   
      
       sprintf(xoverres,"%ld\t%s\t%s\t%s\t%s\t%s\t\t" CRLF,   
      
   and replace it with   
      
       sprintf(xoverres,"%ld\t%s\t%s\t%s\t%s\t%s\t\t\t" CRLF,   
      
   note the additional "\t" at the end of the quoted section...   
      
   i found this bug with the XPN news reader that's written in python... it uses   
   the nntp library in python and was returning a data error alert... adding the   
   additional "\t" to the line filled in that last field with the empty data it   
   was looking for and now i have anohter news reader that seems to work pretty   
   well...   
      
   )\/(ark   
      
    * Origin: news://news.wpusa.dynip.com | acct req'd to post (1:3634/12)