You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Rustam Aliyev (JIRA)" <ji...@apache.org> on 2012/11/24 02:38:58 UTC
[jira] [Updated] (PROTOCOLS-98) Decouple POP3 UID forming logic
from protocol implementation
[ https://issues.apache.org/jira/browse/PROTOCOLS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rustam Aliyev updated PROTOCOLS-98:
-----------------------------------
Attachment: protocols98.patch
Hi Eric, attached, see protocols98.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
>
> Attachments: protocols98.patch
>
>
> 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