The Jakarta Mail API provides a platform-independent and protocol-independent framework to build mail and messaging applications. The Jakarta Mail API is available as an optional package for use with the Java SE platform and is also included in the Jakarta EE platform and the Java EE platform.
NOTE: The documentation for the implementation of this specification, Angus Mail, is available here, the documentation for older versions, Jakarta Mail/JavaMail, is available here
The 2.1.3 release is a bug fix release of the Jakarta Mail project in the 2.1.x line, and includes several bug fixes and enhancements. See the changelog for details.
The 2.1.2 release is a bug fix release of the Jakarta Mail project in the 2.1.x line, and includes several bug fixes and enhancements. See the changelog for details.
The 2.1.1 release is a bug fix release of the Jakarta Mail project in the 2.1.x line, and includes several bug fixes and enhancements. See the changelog for details.
The 2.1.0 release breaks the tight integration between Jakarta Mail Specification API and the implementation and provides standalone API jar file only. The implementation itself, formerly JakartaMail, is now standalone project - Eclipse Angus. This version of the specification is included in the Jakarta EE 10 Platform.
To break tight integration between Jakarta Mail Specification API and the implementation, sources of the implementation were moved to the new project - Eclipse Angus - and further development continues there. Eclipse Angus is the direct successor of JavaMail/JakartaMail.
The 1.6.7 release is a bug fix release of the Jakarta Mail project in the 1.x line, and includes several bug fixes and enhancements. The main jar file is located at com.sun.mail:jakarta.mail.
The 2.0.1 release is a bug fix release of the Jakarta Mail project in the 2.x line, and includes several bug fixes and enhancements. The main jar file is located at com.sun.mail:jakarta.mail.
The 1.6.6 release is a bug fix release of the Jakarta Mail project in the 1.x line, and includes several bug fixes and enhancements. The main jar file is located at com.sun.mail:jakarta.mail.
Jakarta Mail 2.0.0 release is the first release with package
namespace changed to jakarta.mail. The main jar file
is located at com.sun.mail:jakarta.mail.
This release contains no other enhancements nor bug fixes,
except for the minimal required Java SE version which is now Java SE 8.
This is also the release included in Jakarta EE 9.
Applications are able to switch to this new version
by just changing all imports that use javax.mail.*
to instead use jakarta.mail.*.
The 1.6.5 release is (hopefully) the last release of the Jakarta Mail project in the 1.x line, and includes several bug fixes and enhancements. The main jar file is located at com.sun.mail:jakarta.mail.
Jakarta Mail, like other parts of Jakarta EE,
is moving to the jakarta.* package namespace.
This is a major change, and so the next release will be Jakarta Mail 2.0.0,
which will be included in Jakarta EE 9.
Applications should be able to switch to this new version fairly easily
by just changing all imports that use javax.mail.* to instead use
jakarta.mail.*.
The 1.6.4 release is the first release of the Jakarta Mail project using the Jakarta EE Specification Process and includes several bug fixes and enhancements. The main jar file is located at com.sun.mail:jakarta.mail.
The JavaMail technology contributed to the Eclipse Foundation has been renamed to “Jakarta Mail” to reflect its role in the Jakarta EE platform.
The 1.6.3 release is the first release of the Eclipse project for JavaMail and includes no bug fixes or enhancements. It does include changes to the Maven coordinates. The main jar file is now located at com.sun.mail:jakarta.mail.
The JavaMail project is now hosted at the Eclipse Foundation as part of the EE4J project.
The Jakarta Mail API is defined through the Jakarta EE Specification Process.
The Jakarta Mail specification and API documentation are available here.
Note that Jakarta Mail 1.6 is identical to JavaMail 1.6.
The JavaMail 1.6 and earlier API is defined through the Java Community Process as JSR 919.
The following documents summarize the API changes in each release of the JavaMail API specification:
Please read the Jakarta Mail FAQ! Read it again. Tell everyone you know to read it. Thank you!
You can post questions to the mail-dev mailing list.
Or, post a question on Stack Overflow using the javamail tag.
Jakarta Mail API bugs are tracked in the GitHub Jakarta Mail project issue tracker.
From time to time snapshot releases of the next version of Jakarta Mail Specification API under development are published to the Jakarta Sonatype OSS repository. These snapshot releases have received only minimal testing, but may provide previews of bug fixes or new features under development.
For example, you can download the jakarta.mail-api.jar file from the Jakarta Mail 2.1.1-SNAPSHOT release here. Be sure to scroll to the bottom and choose the jar file with the most recent time stamp.
You’ll need to add the following configuration to your Maven ~/.m2/settings.xml to be able to use these with Maven:
<profiles>
<!-- to allow loading Jakarta snapshot artifacts -->
<profile>
<id>jakarta-snapshots</id>
<pluginRepositories>
<pluginRepository>
<id>jakarta-snapshots</id>
<name>Jakarta Snapshots</name>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
<checksumPolicy>fail</checksumPolicy>
</snapshots>
<url>https://jakarta.oss.sonatype.org/content/repositories/snapshots/</url>
<layout>default</layout>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
And then when you build use mvn -Pjakarta-snapshots ....
If you want the plugin repository to be enabled all the time so you don’t need the -P, add:
<activeProfiles>
<activeProfile>jakarta-snapshots</activeProfile>
</activeProfiles>
By contributing to this project, you agree to these additional terms of use, described in CONTRIBUTING.