> I joined this list to figure out how to best integrate James.
> The only thing I can think of now is being able to dynamically
> add/remove users and aliases from James from my application. If
> those methods were available within our application, it could make
> things very easy.
People have written code to use the telnet interface for this purpose.
Alternatively, there is an RMI proposal, but it is not part of the main
code.
> I don't know how well James supports JMX and JNDI, but if these
> methods are accessible remotely I'd be living a dream. If not,
> I'd be interested in aiding in that area.
We always welcome contributions, and JMX would be a useful area. JNDI is
something I plan to work on as soon as v2.2 ships, and would welcome others.
> The only advantage I might seeembeding James is runnig only 1 process.
Ironically, I plan to setup James as 3+ processes, and post a sample
configuration for that approach. SMTP, POP3 and SMTP would each run in
their own process, as would the mailet pipeline. One advantage is that one
can reconfigure the pipeline, and restart just that process, without
impacting any transactions. Another is the ability to run the mailet
pipeline without root privilege.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
