DO NOT REPLY [Bug 13564] New: - Assorted NNTP Protocol Bugs

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13564>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13564

Assorted NNTP Protocol Bugs

           Summary: Assorted NNTP Protocol Bugs
           Product: James
           Version: 2.0a3
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: NNTPServer & Repository
        AssignedTo: james-dev@jakarta.apache.org
        ReportedBy: farsight@alum.mit.edu


There are a bunch of outstanding NNTP protocol bugs.

1. Use of STAT, ARTICLE, HEAD, or BODY with an article number argument does 
not properly set the current article pointer to the current value.

2. For empty groups the current article pointer is set to 0 rather than being 
left invalid when the LISTGROUP or GROUP commands are used.  This is contrary 
to RFC 2980.

3. For the NEWNEWS or NEWNEWSGROUP commands an absent or ill-formed date 
parameter is improperly handled.  A response indicating data will be sent is 
delivered to the client, and then a NPE is generated, resulting in a close of 
the connection.  Instead, the server should return a 501 syntax error

4. OVER/XOVER is provided by the server, but the LIST OVERVIEW.FMT is not 
supported, contrary to the strong recommendations of RFC 2980

I've got fixes for all of these - am waiting for the current discussion of 
server architecture to resolve before I post them.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: DO NOT REPLY [Bug 13564] New: - Assorted NNTP Protocol Bugs

[Harmeet Bedi <ha...@kodemuse.com>]

----- Original Message -----
From: <bu...@apache.org>
>            Summary: Assorted NNTP Protocol Bugs
>         ReportedBy: farsight@alum.mit.edu
...
> I've got fixes for all of these - am waiting for the current discussion of
> server architecture to resolve before I post them.

Peter,
If these bugs can be resolved without restructuring code, you should check
them in.

If you need to rearchitect or refactor for these fixes, you should post your
proposal and your fixes.

Harmeet


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>