> > I'm not a committer > > Keep working. You could be. :-) I'll be, for sure :-)
> > There are no many differences with the current 2.2.1-dev to > switch to > > a > 3.0 > > and I think that it is backward compatible with 2.2.x, isn't it? > > Well, there are many things that can be done with this code > base. In my view, POJO is not the highest priority. POJO is not high priority for me too. My priorities are: 1- Full DSN support (SMTPServer, Delivery Mailets/Processor, MailImpl) 2- RemoteDelivery: reuse/sort connections to the same hosts (mass delivery) 3- RemoteDelivery: better error handling based on specific ESMTP / DSN reply codes. 4- Spooler: improve match/mailet speed and movement between processors. 5- S/MIME: new Mailets to check signature, encrypt/decrypt and more. 1 and 4 require changes in the core, 2-3 and 5 are only mailet changes. I'm in progress in every point and currently mantaining my own branch. I also think that POJO (with support for Spring) and a JMS interface for the Spooler would be useful to improve the userbase of James and I hope userbaso grown because I don't want to be tied to a deprecated mail server ;-) Most of my priorities will not require a 3.x change (backward compatibility can be mantained). Jdk1.4, POJO, Mailet API refactoring and this kind of changes will instead require a 3.x branch. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
