Okay. I don't think its very important but could be to others. Since JAMES is the server and it will be perceptually JAMES's mailets and not just Apache Mailets it might kind of inhibit adoption. I don't really care enough to be personally inhibited, just pointing out that it is an inhibition.
Cool, appreciated. If we did this, I'd expect we'd keep this in the same project in ASF, though a rename from James to Email might make sense. That's unchartered territories though, and I'd rather not deal with it too much if we can avoid it.
Otherwise everything you said sounds good.
I have no emotional attachment to JavaMail, and it does suck as a server and performance-concerned API. Actually, it largely sucks as a client API either, but at least that's what it was trying to do. I'd love to have a better API geared towards these issues, but I'm leery of the work it would take to comply with the undocumented real-world SMTP/mime spec.
We've just added some committers to James to incoporate MIME4j (currently at http://mime4j.sourceforge.net/). Maybe we consider using that.
-- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
