The IMAP work is currently stalled (as people may have noticed) because I have so little time to work on it. There is a key blocking requirement that must be resolved before I can proceed: The James repository must be made into a proper hierarchical store a la ImapStore IIRC. Without this I'm a bit stuck.
If someone does this then there shouldn't be much work to get IMAP going properly. This doesn't require an in-depth knowledge of the IMAP RFC's but does require enough knowledge of James to understand what needs to be changed in the repository model. People can implement interfaces to IMAP forever but without this piece they will never be complete. -- Jason > -----Original Message----- > From: Zsombor [mailto:[EMAIL PROTECTED] > Sent: 20 October 2005 13:36 > To: [email protected] > Subject: IMAP status > > Hello ! > > In the recent years I saw some attempts to implement IMAP support in > James. > However as far as I know, none of them succeed. So I would like to ask > some > question about > Is there anyone who still working on it ? If noone, then why it's > abandoned? > How good the current code? Is it usable for at least, to view folders / > mails ? Which commands implementation is missing? Or the James's > MailStorage > interface is not sufficiently powerful to accomplish some of the features. > What is the main blocker to improve the situation? > I've tried to read the RFC-s, but those are lengthy and complex novels, > not > an easy reading :-) > > BR, > Zsombor --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
