NNTP Transport provider does not correctly store message identifiers --------------------------------------------------------------------
Key: GERONIMO-4252 URL: https://issues.apache.org/jira/browse/GERONIMO-4252 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: mail Reporter: David Graff Priority: Minor While working with a client program I used the 1.6-SNAPSHOT (built locally) and noticed a problem where the message ID was not correctly identified to the NNTP server I was communicating with. When recieved in the message processor, the < and > are stripped off and the "meat" of the id are stored. When performing a "STAT" call, the < and > are not restored resulting in a news server error. Referencing the NTTP RFC 3977 (http://tools.ietf.org/html/rfc3977) Section 3.6 it states the following regarding message IDs {quote} Each article MUST have a unique message-id; two articles offered by an NNTP server MUST NOT have the same message-id. For the purposes of this specification, message-ids are opaque strings that MUST meet the following requirements: o A message-id MUST begin with "<", end with ">", and MUST NOT contain the latter except at the end. o A message-id MUST be between 3 and 250 octets in length. o A message-id MUST NOT contain octets other than printable US-ASCII characters. {quote} As this states, the < and > are required. There are two ways this can be accomplished, 1, store the message ID with the < and > in NNTPGroupFolder or change all calls using the message ID to encapsulate with < and >. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.