Hi, Thanks for the feedback :) Beside that you were right with the invalid UIDs in the FETCH response. I committed a fix for this today to act like other imapserver do..
Bye Norman 2010/9/13, Francois-Denis Gonthier <[email protected]>: > Hello Norman and server-dev > > With new knowledge in mind, I have reworked my UID management and things > seem to work better now! There was nothing wrong with the UidToMsnConverter. > > -- > François-Denis Gonthier > Programmeur/analyste > 819-780-8955 #1128 http://www.revolutionlinux.com/ > > ----- Mail original ----- >> Hi Francois-Denis, >> >> >> 2010/9/12 Francois-Denis Gonthier <[email protected]>: >> > Now, I still think getMsn returning -1 is a problem. If the >> > processor asks for a mail which the UidToMsnConverter doesn't know, >> > it returns -1 and that number happens to be sent down the wire in a >> > FETCH response. This confuses the IMAP client which usually >> > disconnects from the server. If you don't happen to have a verbose >> > IMAP trace running, the problem might be totally invisible by the >> > client. I would prefer a big fat exception be thrown on unknown >> > message than this. >> > >> >> I agree we should at least take some care here in FetchProcessor. >> >> Could you fill a JIRA issue for it ? >> https://issues.apache.org/jira/browse/IMAP >> >> Thx, >> Norman >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
