You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Ersin Er <er...@ata.cs.hun.edu.tr> on 2005/03/16 20:35:38 UTC
Slow data flow from James NNTP server, or what?
Hello,
We are newbie users of Apache James. We only want to use it as an NNTP
server. We've installed, configured and started it.
When we create an acoout with our news client and get the groups list,
the comes without any problems. However, 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_. Article's header comes but the body does not
(or it also comes but the client does not display it for some reason).
We have seen this problem only with James.
Could you please help?
--- Ersin Er
RE: Slow data flow from James NNTP server, or what?
Posted by Daniel Perry <d....@netcase.co.uk>.
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:noel@devtech.com]
> 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: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: Slow data flow from James NNTP server, or what?
Posted by "Noel J. Bergman" <no...@devtech.com>.
> 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: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org