Wednesday, January 17, 2007

Mailet API getting some independance

In the past the Mailet API has been managed within the Apache James Server project. You could always get the api separately but it was managed in the James Server lifecycle.

Today the votes were counted and the API will soon be taking its rightful place as a James subproject.

We'll start small, by releasing the current version, and move on to look at the enhancements we've been discussing over on

Eventually I hope we'll add things like a Reference implementation independent of James Server and suitable for embedding, an SDK, and possibly a TCK.

If you want to get involved subscribe to and speak up.


blog comments powered by Disqus

I know nothing, I'm not a fortune teller, and you'd be insane to think that I am. This disclaimer was cribbed from an email footer I once received. It is so ridiculous I had to have it for myself.

Statements in this blog that are not purely historical are forward-looking statements including, without limitation, statements regarding my expectations, objectives, anticipations, plans, hopes, beliefs, intentions or strategies regarding the future. Factors that could cause actual results to differ materially from the forward looking statements include risks and uncertainties such as any unforeseen event or any unforeseen system failures, and other risks. It is important to note that actual outcomes could differ materially from those in such forward-looking statements.

Danny Angus Copyright © 2006-2013 (OMG that's seven years of this nonsense)