Hi,
We have PROTOCOLS-98 (Decouple POP3 UID forming logic from protocol
implementation) in the pipe to fix this.
Before committing PROTOCOLS-98, we IMAP-351 must be pushed.
Thx, Eric
On 09/11/2012 09:13, Jan Chaloupecky wrote:
Hi,
I'm working on a POP3 proxy and I'm using James for the server side of my
program. I see that the MessageMetaData object defines the POP3 message id
as a long
http://james.apache.org/protocols/apidocs/org/apache/james/protocols/pop3/mailbox/MessageMetaData.html
My question is why is this id a long and not a String ? The POP3 RFC
extension clearly defines this ID as a String.
http://www.ietf.org/rfc/rfc1939.txt
The problem I have is that my software, working as a pop3 proxy, cannot
simply sent the server uid (string) to the component handled my James since
the api expects a long
cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
