Use the links below to download the product from one of our mirrors. You mustverify 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.
[if-any logo]
[end]
The currently selected mirror is [preferred]. 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.
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
using
% pgpk -a KEYSor
% pgpv james-version.tar.gz.asc
% pgp -ka KEYSor
% pgp james-version.tar.gz.asc
% gpg --import KEYS
% gpg --verify james-version.tar.gz.asc
This release has many enhancements and bug fixes over the previous release. See the Release Notes for a detailed list of changes. Some of the earlier defects could turn a JAMES mail server into an Open Relay. All users of JAMES Server are urged to upgrade to version v2.3.1 as soon as possible.
Are now archived.
Apache Mime4J 0.6 is the latest stable version:
Apache James jSPF 0.9.7 is the latest jSPF stable version:
Apache JSieve 0.3 is the latest stable version:
Apache Mailet 2.4 is the latest stable version:
Apache Mailet Base 1.0 is the latest stable version:
Apache Crypto Mailets 1.0 is the latest stable version:
Apache MPT 0.1 is the latest stable version:
The software listed above represents the latest Release Build available from the Apache JAMES Project.
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.