[ https://issues.apache.org/jira/browse/PROTOCOLS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503158#comment-13503158 ]
Eric Charles commented on PROTOCOLS-98: --------------------------------------- Hi Rustam, Finally I will not commit the IMAP-351 patch, so it will be good that you attach your patch here. Thx, Eric > Decouple POP3 UID forming logic from protocol implementation > ------------------------------------------------------------ > > Key: PROTOCOLS-98 > URL: https://issues.apache.org/jira/browse/PROTOCOLS-98 > Project: JAMES Protocols > Issue Type: Improvement > Components: pop3 > Affects Versions: 1.6.1 > Reporter: Rustam Aliyev > Assignee: Norman Maurer > Fix For: 1.6.2 > > > Currently, it seems that UID string formation logic is hardcoded into POP3 > protocol. For example, UidlCmdHandler in a number of places forms UID using > Long field from MessageMetaData. > However, RFC1939 defined UID as an arbitrary server-determined string, > consisting of one to 70 characters in the range 0x21 to 0x7E > (http://tools.ietf.org/html/rfc1939#page-12). > POP3 protocol implementation should be able to specify arbitrary UID String > as a part of MessageMetaData alongside with Size. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org