Thanks Daniel. I have here saved the note you are refering to. But
before I touch the source code and recompile James, I wanted to make
sure of the solution. During last week there were other mails where it
was said the problem was on clients side. So I tried to do this test
programming myself the client.
Once again, thank for your comments,
Chemi.
Daniel Perry wrote:
After looking into it a week or so ago, i found that:
RFC's state that it must end in \r\n.\r\n (the message before that doesnt
have to end in anything specific (ie doesnt have to end in new line!!!)
The clients you speak of do send \r\n.\r\n (they just dont necessarily
include a newline after the message which james needs!)
James is broken, because it sends .\r\n at the end of a message. It assumes
that the message ends with \r\n, which accoring to RFCs (and the browsers
you list) this aint the case!
To repeat my solution (which makes james rfc compliant and works) from an
email last week:
NNTPHandler.java line 1504 is:
writeLoggedFlushedResponse(".");
Should be:
writeLoggedFlushedResponse("\r\n.");
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
