We are proud to announce the availability of Apache jSPF-0.9.5. This
release brings initial support for asynchronous processing and is fully RFC4408 compliant.
After almost 2 years the Apache JAMES team is proud to announce the availability of Apache Mime4J 0.3. This is the first release under the ASF umbrella.
Following a decision taken by the James PMC a few months ago, the Apache Mailet API project is now independent of JAMES Server and has its own webpage and its own source repository.
James PMC is proud to announce the availability of the final release of JAMES Server 2.3.1. More informations on what has been fixed since the 2.3.0 release can be found in the changelog.
James PMC is proud to announce the availability of the first release candidate of JAMES Server 2.3.1. This release is maintenance release. See the changelog for more detail.
The James PMC has approved - for the first time - a set of guidelinesfor the project. These guidelines are intended to reflect and summarize well-known practices in our community. They include "... definitions of how conflict is resolved by voting, who is able to vote, and the procedures to follow for proposing and making changes to the Apache JAMES products."
James PMC is proud to announce the availability of the fourth beta of jspf 0.9. This version pass all tests in the last official release of the spf testsuite.
James PMC member and commiter Danny Angus was interviewed about James by David Reid for Feathercast episode 24. You can download the podcast from here.
The James commiters have voted to promote the Mailet API to its own James sub-project.
This move will provide a clearer division between development of the API and development of James server, and we hope this will encourage more participation from external projects.
The effort will start small, by releasing the current version, and move on to look at the enhancements we've been discussing over on the mailet api list where we will extend a warm welcome to anyone who has something to contribute.
Eventually we hope to extend the scope of the sub-project to include things like a Reference Implementation independent of James Server and suitable for embedding, an SDK, and possibly a TCK.
