Is there a reason why JBoss Mail shouldn't adopt the Apache James Mailet /
Matcher API? It seems well documented and is a stable, well thought out API
for e-mail workflow processing.
Honestly, I've looked at (am still looking at) James as an e-mail server
solution for an upcoming project. I
Look, there is very next to no chance we'll use anything from JAMES. The
pieces we DID use from JAMES are being ripped out because they didn't profile
well (namely the layered streams). The mailet API may be well documented but
its frankly not that good. Furthermore the goal is very
I would however encourage an affirmative and positive What I'm looking for.
No one will make you use mail scripting. Just because YOU don't see value in
it doesn't mean others (me for instance) won't. I intend to SYNDICATE my spam
catch scripts and AGGREGATE those of others in my trust
Well BeanShell or whatever is fine so far as scripting but no matter what we
cannot avoid bindings. Meaning supplying WHAT objects should be managed.
JSR-223 seems not perscriptive so far as the scripting langauge. I'm not
against that, but we should have something preferred. I originally
