It strikes me that perhaps I should add the following separately to the "JAMES SMTP API" thread.

The commercial projects in which I have direct involvement would find the following three features to be most useful:

* Standard (supported) access to mail repositories (in any form).
* Improved Mailet deployment. Hot deployment is a nice-to have, but not essential. What is essential is for me to be able to build a simple deployment unit that is easily inserted into JAMES in a clear and defined manner.
* Improved Mailet configuration. Pluggability of config sources, in particular. I would like to be able to get my config from (variously) a RDBMS, an XML file, or the JAMES init params.

Cheers

ADK


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to