james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rustam Aliyev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTOCOLS-98) Decouple POP3 UID forming logic from protocol implementation
Date Sat, 27 Oct 2012 02:59:12 GMT

    [ https://issues.apache.org/jira/browse/PROTOCOLS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485335#comment-13485335

Rustam Aliyev commented on PROTOCOLS-98:

Ok. I'll wait for your changes to be commited, then attach fresh patch.
> 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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message