> Along with the refactoring, can we begin including tiny bits > of IMAP support code and marking those experiment, and turned > off by default?
IIRC current IMAP support does not persist messages. This is a blocking issue. We can add it when it is at least working (also with limits). > Currently, I am looking at pulling the > IMAP code out of Foedus > [ http://sourceforge.net/projects/foedus ] and maybe > integrating with MINA and using that as a base for a simple > IMAP only server. Alternatively, we can work together. I don't understand what is the Foedus License. Do you know that? I don't know much of our experimental IMAP but it seems to me that our imap is more advanced than the code inside foedus. BTW foedus does use avalon too and should be not too difficul to create a block working inside james. > Having IMAP locked away in its own > branch secludes the effort from the rest of the project and I > think that's at least partly why it hasn't been done yet. > That, and the fact that there hasn't been an *authorative* > detailed plan on how to get that subproject completed. I don't have many interests in IMAP and I don't know much of IMAP protocol, BTW I am here if you need support about james and hints on james architecture. Indeed, It would be cool to have preliminary IMAP support in the next james release. I've seen many developers asking for the status in this list, maybe there is only needs for a lead. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
