Hello,
Last I looked at IMAP proposal, it required the
completion of a hierarchial message store.
As far as I can remember...
James uses a flat message storage interface,
which is fine for POP and SMTP, but inadequate
for IMAP. Someone wrote a hierachial message
storage interface that keeps the entire store
in memory, but no one had, at the time written
an implementation of that interface on persistant
storage ( file or db ). Then, there was also
some talk of consolidating some of the
repository/mailstore/etc interfaces found
around the source tree.
I started on a generic 'James-compatible'
message storage interface implemenation, which
sits on Derby, but like everyone else, have
been distracted. I am committed to finishing
my store ( as it is part of a larger project )
but that won't be done for months and months
probably.
Best regards,
Kervin
Stefano Bagnara wrote:
Thom Hehl wrote:
It looks like IMAP4 is in incubation. I'd be interested in helping out
with this implementation. Where do I start? I was poking around, but
it seems the source is a bit difficult to find.
We should add this to our FAQs ;-)
You can start searching through the James archives to understand who
worked on IMAP, where the current sources are, what is missing and why.
I never worked with IMAP, so I can't help too much.
Stefano
---------------------------------------------------------------------
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]
