I agree with the latter, but the former is addressed by the aforementioned
in-protocol handlers. Perhaps you're just behind the times with JAMES.
I respectfully disagree Noel.
I don't wish to talk about JAMES. Not because I don't value it as a
project but because IMHO it has no purpose on a discussion list about
the Mailet API.
We no more want to talk about Tomcat or JBoss when it comes to
discussing the Servlet API. JAMES is merely *one* container
implementation of the Mailet API - we now have an alternative
implementation in MailCatcher.
JAMES is probably suffering from being only the rooster in the farm; but
that is something we would like to address and offer people a choice
when it comes to Mailet containers.
If one wants to use the Servlet API again as an example, i see JAMES as
the full blown "J2EE" reference implementation, where as the Mailet
stuff, is like the Servlet Containers (ServletExec, Tomcat etc).
So the question boils down to this; does one want to see the Mailet API
grow as a separate project, or is this really a JAMES discussion?
