G'day Darrell,
Sounds good, I'll have a peak at the imap2 proposal. Then I can ask you for help when needed.
I think it would be nice to have IMAP storage for the 2.x version. Is the current mail storage preventing this?
- Christian
Darrell DeBoer wrote:
*This message was transferred with a trial version of CommuniGate(tm) Pro*
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.
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
