Yes.
MessageMetaData constructor validates new metadata records using
following function:
https://github.com/rstml/james-protocols/blob/26f98a3a783dfe4bffeca8aaded88ffa6066b653/pop3/src/main/java/org/apache/james/protocols/pop3/core/MessageMetaDataUtils.java#L54
--
Rustam
On 24/10/2012 16:24, Eric Charles wrote:
Thx.
Does your patch enforce the RFC: "The unique-id of a message is an
arbitrary server-determined string, consisting of one to 70 characters
in the range 0x21 to 0x7E" ?
Eric
On 20/10/2012 22:37, Rustam Aliyev wrote:
Hi Eric,
Thanks. The main reason I'd say is RFC compatibility. I believe it will
help to make James Protocols more popular if it will comply with RFCs.
In my particular case, we are adding POP3 support to ElasticInbox
through James Protocols and our UID is Base64 encoded UUID.
Many thanks,
Rustam.
On Sat Oct 20 18:07:44 2012, Eric Charles wrote:
Hi Rustam,
I will provide feedback on the JIRA for Monday.
I remember you were using String instead of int for uid. Any
particular reason?
(better use James Developers List <server-...@james.apache.org>
mailing list for further communication, see
http://james.apache.org/mail.html)
Thx, Eric
On 20/10/2012 13:50, Rustam Aliyev wrote:
Hi,
I'm not sure if this is the right place to ask. I submitted patch for
POP3
a week ago - https://issues.apache.org/jira/browse/PROTOCOLS-98
Could someone provide any feedback please?
Many thanks,
Rustam.
