Max,
IMAP support at the protocol level is present in one of the proposals. Missing is repository support. More importantly, missing are interested parties eager to work on IMAP support.
Development on James has been anything but stalled. There has been constant and active James development at a pretty good clip. There are quite a few things actively in the pipeline as we speak, with more contributors than before.
Sorry: wasn't meaning to imply that devel on *James* had stalled, only IMAP devel... If I thought James devel had stalled, I wouldn't bother emailing the list at all! It's exactly because it's an active (and interesting project), that I have been looking at it.
The issue with IMAP is that we need to get the new repository structures going for James v3, and we need people whose interest is IMAP rather than high performance mailing list delivery, anti-SPAM, administration, or what-have-you.
If that's the case, as I do want to use James, and won't use it until it has IMAP, I shall have a look into the internals of it's IMAP, and see what I can do. Have you tips as where is best to start, or should I just immerse myself, and see what I think needs improving most?
--- Noel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- [M. Grender-Jones www.hesperides.net] [Mobile: 07714 762 940 Stationary: 020 76072868] [EMAIL PROTECTED] ICQ# 28467015]
If at first you don't succeed, failure may be your style.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
