Use the links below to download the Apache JAMES products from one of our mirrors. You must verify the integrity of the downloaded files using signatures downloaded from our main distribution directory.
Only current recommended releases are available on the main distribution site and its mirrors. Older releases are available from the archive download site.
The currently selected mirror is http://mirror.cc.columbia.edu/pub/software/apache/. If you encounter a problem with this mirror, please select another mirror. If all mirrors are failing, there are backup mirrors (at the end of the mirrors list) that should be available.
You may also consult the complete list of mirrors.
Apache JAMES server 2.3.1 has been released and no new unstable releases have been released. Please go to the stable releases download page to download it.
Apache JAMES jSPF 0.9.6 has been released and no new unstable releases have been released. Please go to the stable releases download page to download it.
Apache Mime4J 0.4 has been released an no new unstable releases have been released. Please go to the stable releases download page to download it.
It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures.
The PGP signatures can be verified using PGP or GPG. First
download the KEYS
as well as the
asc signature file for the particular
distribution. Make sure you get these files from the main distribution
directory, rather than from a mirror. Then verify the signatures
% pgpk -a KEYS
% pgpv james-version.tar.gz.asc
% pgp -ka KEYS
% pgp james-version.tar.gz.asc
% gpg --import KEYS
% gpg --verify james-version.tar.gz.asc
The software listed above represents the latest unstable builds
available from the Apache JAMES Project.
You can download Stable Releases here.
Unstable releases are announced on the General mailing list (firstname.lastname@example.org).
The JAMES project also provides Nighly Builds: periodic snapshots during development. Generally, these are considered stable snapshots, but they have not undergone as much testing as a Release Build, nor have they been voted upon for release by the developer community. These are simply convenient test builds. Sometimes the purpose for a Nightly Build could be soliciting feedback on a specific change.