pgoldstein 2002/12/11 13:44:18
Modified: src/xdocs todo.xml
Log:
Updating the TODO list. Reorganized based on functional area, rather than
"priority". A number of items were substantially fleshed out.
Revision Changes Path
1.8 +68 -28 jakarta-james/src/xdocs/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/jakarta-james/src/xdocs/todo.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- todo.xml 20 Apr 2002 19:12:10 -0000 1.7
+++ todo.xml 11 Dec 2002 21:44:17 -0000 1.8
@@ -6,50 +6,90 @@
<title>TODO</title>
<author email="[EMAIL PROTECTED]">Serge Knystautas</author>
<author email="[EMAIL PROTECTED]">Charles Benett</author>
+ <author email="[EMAIL PROTECTED]">Peter M. Goldstein</author>
</properties>
<body>
<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 20 April 2002.</p>
+Last Updated 10 December 2002.</p>
</section>
-<section name="High Priority">
-<p>Refactor to use the latest Avalon releases.</p>
+<section name="Cross-Service Issues">
<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>
+<p>Revisit UserRepository. The interface must support multiple authentication
types per user,
+aliasing (both local and non-local), as well as per-user quotas. It may be
desirable to be able
+to associate attributes with users in the repository.</p>
+<p>Revisit the MailRepository interface and associated implementations. Special
consideration is
+necessary to support IMAP Search functionality. It should be possible to associate
attributes
+with mail messages stored in the repository.</p>
+<p>Revisit the SpoolRepository implementations and do away with the current
exception-generating
+two-phase message retrieval.</p>
+<p>Define a simple mechaism for addressing repositories in a uniform way.</p>
+<p>Add support for mbox mail file repository.</p>
+<p>Add support for the <a href="http://cr.yp.to/proto/maildir.html";>maildir</a>
file repository.</p>
+<p>Add support for DRAC login/relay authorization. This feature records the IP
addresses and times of
+POP3 logins. SMTP connections from these same IP addresses are considered
authenticated if they occur
+within a fixed period of the POP3 authentication.</p>
+<p>Develop repository migration tools so that users of the old repositories can
easily migrate to newer repositories.</p>
+</section>
+
+<section name="SMTP Service">
+<p>Add support for the enhanced status codes extension (<a
href="http://www.faqs.org/rfcs/rfc2034.html";>RFC 2034</a>).</p>
+<p>Add support for the 8BITMIME extension.</p>
+<p>Expand the SMTP server so it supports a variety of SASL authentication
mechanisms.</p>
+<p>Complete support for delivery service notification (<a
href="http://www.faqs.org/rfcs/rfc1891.html";>RFC 1891</a>).</p>
+<p>Discuss optional support for VRFY and EXPN.</p>
+<p>Discuss some form of spam filtering that would allow filtering before messages
are fully read in from the network.</p>
+</section>
+
+<section name="IMAP Service">
+<p>Get IMAP server to alpha standard (i.e. basic interoperation with e-mail
clients).</p>
+<p>Add #news namespace to IMAP system</p>
+</section>
+
+<section name="POP3 Service">
+<p>Give admins the option to enforce one access at a time to a POP3 mailbox.</p>
+</section>
+
+<section name="NNTP Service">
+<p>Refactor NNTP code base.</p>
+<p>Tie in the NNTP Repository with POP/SMTP/IMAP repository structure.</p>
+</section>
+
+<section name="List Management">
+<p>Write a list server implementation with functionality comparable to ezmlm. This
would include
+the capability to handle multiple lists of 100,000+ members, double opt-in
subscription mechanisms,
+and a full suite of mail-driven commands.</p>
+</section>
+<section name="Avalon Integration">
+<p>Update code base to use Serviceable/ServiceManager rather than
Composable/ComponentManager. This
+requires an effective change in how we expose components through the Mailet API.</p>
+</section>
+
+<section name="Mailet API">
+<p>Discuss and design the next revision of the Mailet API.</p>
</section>
-<section name="Medium Priority">
+<section name="DNS Server">
+<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>
+</section>
+<section name="SpoolManager">
+<p>Add support for better mailet router/processing (maybe like RequestDispatcher) -
Use Stage/Pipeline pattern</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 for deployable message processing apps using Camelot pattern</p>
+</section>
+
+<section name="Remote Management">
+<p>Rewrite RemoteManager to be an exposed 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>Take advantage of Phoenix JMX capabilities to enable more complete measurement
of James behavior.</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>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 (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>
-<p>Tie in the NNTP Repository with POP/SMTP/IMAP repository structure.</p>
-<p>Test and move RMI interface from proposal directory to main branch.</p>
</section>
-<section name="Low Priority">
-<p>Add support for DRAC login/relay allowing</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 name="Documentation">
+<p>Document instructions on configuring logging in James.</p>
</section>
</body>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
