Re: IMAP Development Pointers

2003-09-03 Thread Jim Wright
Hi Edward, Edward Flick wrote: Just out of curiosity, is there anything wrong with just using the filesystem? Folders work wonders :-P. And sets of enumerated files for messages would be nice, easy, and quick to implement, and I guess some quick and easy link file for common boxes between accou

Re: IMAP Development Pointers

2003-09-03 Thread Serge Knystautas
Edward Flick wrote: Just out of curiosity, is there anything wrong with just using the filesystem? Folders work wonders :-P. And sets of enumerated files for messages would be nice, easy, and quick to implement, and I guess some quick and easy link file for common boxes between accounts. What do

RE: IMAP Development Pointers

2003-09-03 Thread Edward Flick
Just out of curiosity, is there anything wrong with just using the filesystem? Folders work wonders :-P. And sets of enumerated files for messages would be nice, easy, and quick to implement, and I guess some quick and easy link file for common boxes between accounts. What do you think? Of cours

RE: IMAP Development Pointers

2003-09-03 Thread Noel J. Bergman
Edward, That would be great. We've had a number of developers "threaten" ;-) to work on IMAP, but no one has really stepped up to it other than DdB. AFAIK, the big problem is the lack of an adequate message store for the hierarchy. I am starting to work on JNDI/LDAP stuff. I will bring it on-l

IMAP Development Pointers

2003-09-03 Thread Edward Flick
I was just wondering what needs to be done as far as getting IMAP support to at least a beta phase. I am willing to code some for it, but a quick ramp up on the situation would be nice if anyone would care to provide it. - To un

cvs commit: james-server/src/java/org/apache/james/transport/mailets Forward.java

2003-09-03 Thread vincenzo
vincenzo2003/09/03 08:44:43 Modified:src/java/org/apache/james/transport/mailets Forward.java Log: Resynchronized allowed values of getRecipients() with AbstractRedirect Revision ChangesPath 1.20 +2 -2 james-server/src/java/org/apache/james/transport/mailets/Fo

cvs commit: james-server/src/java/org/apache/james/transport/mailets Forward.java

2003-09-03 Thread vincenzo
vincenzo2003/09/03 08:18:25 Modified:src/java/org/apache/james/transport/mailets Tag: branch_2_1_fcs Forward.java Log: Resynchronized allowed values of getRecipients() with AbstractRedirect Revision ChangesPath No revision No

RE: AbstractRedirect family: Reply-To handling

2003-09-03 Thread Vincenzo Gianferrari Pini
I just committed an update to AbstractRedirect, Redirect and Resend to handle a new "replyTo" value that can be used in the and parameters (and/or returned by getRecipients() and getTo() in subclasses. The behaviour is as specified in RFC 2822: Reply-To defaulting to From defaulting to Sender.

cvs commit: james-server/src/java/org/apache/james/transport/mailets AbstractRedirect.java Redirect.java Resend.java

2003-09-03 Thread vincenzo
vincenzo2003/09/03 04:14:05 Modified:src/java/org/apache/james/transport/mailets Tag: branch_2_1_fcs AbstractRedirect.java Redirect.java Resend.java Log: 1) Added support for "replyTo" in getRecipients and getTo. 2) Minor javadoc enha

cvs commit: james-server/src/java/org/apache/james/transport/mailets AbstractRedirect.java Redirect.java Resend.java

2003-09-03 Thread vincenzo
vincenzo2003/09/03 04:10:10 Modified:src/java/org/apache/james/transport/mailets AbstractRedirect.java Redirect.java Resend.java Log: 1) Added support for "replyTo" in getRecipients and getTo. 2) Minor javadoc enhancements. Revision ChangesPath 1