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.
-----Original Message-----
From: Chemi [mailto:[EMAIL PROTECTED]
Sent: 18 October 2004 15:52
To: James Users List
Subject: Re: Problem reading posts from NNTP server
To add some info... I have develop a simple test case where I post a NNTP
message using Jakarta-Commons-net and I have to force a \n\n at the end of
the body to read it later without problems. If I don't send "\n\n" at the
end.... I have again the same problem.
I have tested "\n" and I have problems reading the post. And when finally
(timeout) I read it, there is a new "." at the end.
I have tested "\n.\n" and I have also problems reading the post. And when
finally (timeout) I read it, there is a new "\n.." at the end.
So the solution is to send "\n\n". And my question here is: are really
Mozilla, FireBird, Jakarta Common Net wrong? or is James wrong?
I will try to read the RFCs because there is something I don't understand.
If I send "\n.\n" it should work and it doesn't.
Thanks in advance,
Chemi.
Noel J. Bergman wrote:
Guys,
If some of you would like to help contribute to the NNTP handling, that
would be great. Please note that we stick to the RFC specifications. In
this case, RFCs 977 and 850 apply.
According to RFC 977, section 3.10.2 (and related), the article being posted
must end with <CR-LF>.<CR-LF>.
some clients arnt sending the first CRLF, so when the message gets sent
back, it doesnt include the CRLF on the end?
What are they sending? The bug report,
http://nagoya.apache.org/jira/browse/JAMES-311, says that they are sending
<CRLF>.<CRLF>, but not <CRLF><CRLF>.<CRLF>. The latter is not necessary.
If the code is not working properly for the former, then it is a bug in the
code.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
