so I've compiled the protocols-pop3 with the pull request from PROTOCOLS-98 and it works as expected. I don't use any imap so I can integrate the lib in my project ;)
On Fri, Nov 9, 2012 at 1:45 PM, Jan Chaloupecky <[email protected]> wrote: > Hi Eric, > thanks for your answer. I'll wait for those issues to be fixed then. > > cheers > > > On Fri, Nov 9, 2012 at 1:13 PM, Eric Charles <[email protected]> wrote: > >> 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<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<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: >> server-user-unsubscribe@james.**apache.org<[email protected]> >> For additional commands, e-mail: >> [email protected].**org<[email protected]> >> >> > > > -- > Jan > -- Jan
