I believe this is being caused by a bug that I previously solved where if a message doesn't end with \r\n (some clients add this, some don't - rfc doesn't specify) james returns it terminating with .\r\n not \r\n.\r\n , so the client never realises it's then end of message!
see patch below which makes james handle this in a rfc compliant manner. ps. noel, can you commit please :) bug is: http://issues.apache.org/jira/browse/JAMES-311 Daniel. --- NNTPHandler_orig.java +++ NNTPHandler.java @@ -1053,7 +1053,7 @@ if (article != null) { writer.flush(); article.writeBody(new ExtraDotOutputStream(outs)); - writeLoggedFlushedResponse("."); + writeLoggedFlushedResponse("\r\n."); } } @@ -1189,7 +1189,7 @@ if (article != null) { writer.flush(); article.writeArticle(new ExtraDotOutputStream(outs)); - writeLoggedFlushedResponse("."); + writeLoggedFlushedResponse("\r\n."); } } > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: 16 March 2005 19:54 > To: James Users List > Subject: RE: Slow data flow from James NNTP server, or what? > > > > We are newbie users of Apache James. We only want to use it as an > > NNTP server. We've installed, configured and started it. > > Fair warning. I love JAMES, but the NNTP support is weak. > Functional, but weak and not as actively developed. I'd like to > see that change. > > > when we post an article and after when we select it from the list > > to see the details we wait for minutes to see its _body_. > > I don't recall seeing that, but try tuning the polling rate for > the NNTP private spool. Did I mention that the code needs > further development? > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
