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 se...@apache.org on 2002/04/20 21:12:10 UTC
cvs commit: jakarta-james/src/xdocs todo.xml
serge 02/04/20 12:12:10
Modified: src/xdocs todo.xml
Log:
Tried to bring current... removed some tasks that were done, reprioritized as the user and dev list's interest seems to warrant, and added various new tasks we've identified.
Revision Changes Path
1.7 +17 -11 jakarta-james/src/xdocs/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/jakarta-james/src/xdocs/todo.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- todo.xml 1 Nov 2001 13:59:14 -0000 1.6
+++ todo.xml 20 Apr 2002 19:12:10 -0000 1.7
@@ -12,26 +12,32 @@
<section name="TODO">
<p>This is a living document that will give new and existing volunteers some areas where we need help. As always, any help is appreciated, be it documentation, code, suggestions, or feedback.
-Last Updated 30 October 2001.</p>
+Last Updated 20 April 2002.</p>
</section>
<section name="High Priority">
-<p>Get classloaders working so custom mailets don't have to be in james.bar</p>
-<p>Update and write more documentation, including a) how to setup user accounts for pop3 delivery/retrieval, b) how to setup a database for message storage, c) how to setup a database for user accounts, d) how to write a mailet.</p>
-<p>Make JamesSpoolManager disposable, calling destroy on mailets, for a graceful shutdown.</p>
-<p>Add regex matchers</p>
+<p>Refactor to use the latest Avalon releases.</p>
+<p>Determine a way to support multiple domains.</p>
+<p>Update and write more documentation, including a) how to setup user accounts for pop3 delivery/retrieval, b) how to setup a database for message storage, c) how to setup a database for user accounts, d) how to write a mailet, e) how to setup and use SMTP auth to allow remote delivery for valid users.</p>
+<p>Improve the debugging output, including a) catching that DNS servers are not correct (at least have DNS log channel record DNS server usage)</p>
+<p>Make log files appending and at 'INFO' level (not debug) by default</p>
+<p>Get IMAP server to alpha standard, ie basic interoperation with e-mail clients.</p>
</section>
<section name="Medium Priority">
-<p>Determine a way to support multiple domains</p>
+<p>Get classloaders working so custom mailets don't have to be in james.jar (SK: I suggest adding support for apps/james/classes and apps/james/lib directories and have the MailetLoader and MatcherLoader use these in addition to system level classpath).</p>
+<p>Refactor RemoteManager to be an object that can be controlled via RMI or what have you, and have the remote manager telnet interface make appropriate calls to this interface.</p>
+<p>Add support in the RemoteManager to manage repositories. This includes listing what's in a repository, viewing individual messages, deleting messages, copying messages, and moving messages.</p>
+<p>Implement an imap:// repository implementation. The goal would be to allow you to transfer messages using the RemoteManager from an IMAP account from or to a James message repository.</p>
+<p>Write an ezmlm comparable listserv manager</p>
+<p>Add regex matchers</p>
+<p>Add support in the CharTerminatedInputStream to support read(byte[]) instead of just read().</p>
<p>Fix NNTP authentication</p>
<p>Fix NNTP ssl</p>
<p>Write more documentation. </p>
-<p>Write more documentation. </p>
-<p>Get IMAP server to alpha standard, ie basic interoperation with e-mail clients.</p>
<p>Add #news namespace to IMAP system</p>
<p>Revisit UserRepository - after doing IMAP List & Subscribe</p>
-<p>Add needed functions to RemoteManager, Including Stop and ReConfigure, Reinject mail, Store RemoteManger password securely.</p>
+<p>Add needed functions to RemoteManager, Including Stop and ReConfigure (?), Reinject mail (this should just be copying/moving messages...), Store RemoteManger password securely.</p>
<p>Add support for better mailet router/processing (maybe like RequestDispatcher) - Use Stage/Pipline pattern</p>
<p>Add support for deployable message processing apps using Camelot pattern</p>
<p>Give admins option to enforce one access at a time to a POP3 mailbox.</p>
@@ -40,10 +46,10 @@
</section>
<section name="Low Priority">
-
<p>Add support for DRAC login/relay allowing</p>
-<p>Enable read receipts to be handled properly</p>
+<p>Enable read receipts to be handled properly (?)</p>
<p>Add support for mbox mail repository format.</p>
+<p>Add support for mail.dir (?) repository format.</p>
</section>
</body>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>