You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Sascha Kulawik <sa...@kulawik.de> on 2002/07/24 17:09:52 UTC
Further Development...
Hello,
Ive already written to this Mailinglist about the further Development.
(It's because the Summer-Hole ? :)
I would like to help developing James, especially the IMAP Port.
Are here any Maintainer they could tell me, how I can help to work on it
?
Also I'm interested, why James isn't based on the JavaMail API. I've
seen the problem with the Store and the old IMAP Implementation - a
Mailserver based on the JavaMail API would help to develop different
Protocolls and also to develop different Stores...
Okay,
Greetings,
Sascha Kulawik
Re: Further Development...
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Sascha Kulawik wrote:
> Hello,
>
> Ive already written to this Mailinglist about the further Development.
> (It's because the Summer-Hole ? :)
> I would like to help developing James, especially the IMAP Port.
Great!
>
> Are here any Maintainer they could tell me, how I can help to work on it
> ?
I did the initial work almost 18 months ago. Although it has been
altered in CVS since then. I probably would approach the problem quite
differently now. You might be better off taking a clean sheet approach.
>
> Also I'm interested, why James isn't based on the JavaMail API.
Bits of it are, especially mailets. But the JavaMail API is largely the
client side of mail not the server side.
If you can see places where using the JavaMail API is an improvement,
please point them out.
> I've
> seen the problem with the Store and the old IMAP Implementation - a
> Mailserver based on the JavaMail API would help to develop different
> Protocolls and also to develop different Stores...
That's not very specific.
Charles Benett
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Further Development...
Posted by Vincent Keunen <vi...@manex.be>.
Hi Sascha,
I'm just a reader of the list (not a developer). What I can tell you is
that IMAP would be very much needed by several people (I saw several
messages about that), but I believe the original developer of IMAP is
not working on it anymore.
So basically, I think that your contribution would be much needed, but
you'd have to manage the project probably. Don't expect to much help
from others on that subject (at least at the beginning), just go for it!
Good luck.
Sascha Kulawik wrote:
>Hello,
>
>Ive already written to this Mailinglist about the further Development.
>(It's because the Summer-Hole ? :)
>I would like to help developing James, especially the IMAP Port.
>
>Are here any Maintainer they could tell me, how I can help to work on it
>?
>
>Also I'm interested, why James isn't based on the JavaMail API. I've
>seen the problem with the Store and the old IMAP Implementation - a
>Mailserver based on the JavaMail API would help to develop different
>Protocolls and also to develop different Stores...
>
>Okay,
>
>Greetings,
>Sascha Kulawik
>
>
>
>
--
!try; do()
--
Vincent Keunen, Ir, http://vincent.keunen.net
Manex, rue Wagner 93, BE-4100 Boncelles, Belgium
Our site: http://www.manex.be
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>