G'day, You might want to look at the code in the proposals/imap2 directory. This is a "from-scratch" partial implementation of IMAP, which I was working on late last year. You could work on this, or use the ideas for your own proposal.
The nice things about this proposal (IMHO): 1) No cut-and-paste code 2) SImple architecture 3) Solid, easy to use test harness and test suite (can make changes and test without needing to start James - speeds up development iterations) The state of the code is that all commands are at least partially funcitonal, with basic protocol tests. I can connect to James-IMAP using KMail, check mail, move mail around, copy etc. The huge caveat is that the mail store is *not* persistent at the moment, it just held in memory. This is nice for testing, but not much good in real life ;). Implementing a persistent store wouldn't be too hard, I just wanted to wait to see where the James3 plans were taking us. -- ciao, Daz On Thu, 16 Jan 2003 19:51, Peter Svensson wrote: > I haven't looked at the current codebase for IMAP support in James, but I > feel that if it is not much we might as well start from scratch? > I have to look at the code and IMAP protocol as well before doing some > serious work, but it would be nice to start of and decide what parts of the > protocol to implement first and how to do it. > The IMAP protocol is pretty big and we should start with a subset of it to > get started... > > PS: The weather here in Gothenburg/Sweden has been nice for a few days now, > the sun is shining but the snow is gone though... > > /Peter -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
