Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.11

Apache James (Java Apache Mail Enterprise Server)

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Apache James is a Simple Mail Transfer Protocol (SMTP), Post Office Protocol 3 (POP3) mail transfer agent, and Network News Transfer Protocol (NNTP) news server written in Java. Apache James manages the mailet Application Programming Interface (API), which allows users to write their own mail-handling code to update a database, build a message archive, or filter spam. A matcher determines whether the mailet should process an email in the server. This technology is a complete and portable enterprise mail engine solution based on available open protocols. This technology provides mail servers running on the Java Virtual Machine (JVM).
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.3
Decision Date:	03/27/2024 at 02:56:36 UTC
Aliases:	Apache James Server
Introduced By:	TRM Request
Vendor Name:	Apache Software Foundation (ASF)

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2.3.x	08/15/2009
3.0.x	06/29/2017
3.2.x	11/05/2018
3.3.x	02/08/2019
3.5.x	06/16/2020
3.6.x	04/05/2021
3.7.x	03/01/2022
3.8.x	05/17/2023

Current Decision Matrix (03/19/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2020

CY2021

CY2022

Future>

Release

2.3.x

Unapproved

3.0.x

DIVEST
[4, 5, 8, 9, 12]

Unapproved

3.2.x

Approved w/Constraints
[4, 5, 8, 9, 12]

Approved w/Constraints
[4, 5, 8, 9, 13]

DIVEST
[4, 5, 13, 14, 15]

Unapproved

3.3.x

Approved w/Constraints
[4, 5, 8, 9, 12]

Approved w/Constraints
[4, 5, 8, 9, 13]

DIVEST
[4, 5, 13, 14, 15]

Unapproved

3.5.x

Unapproved

Approved w/Constraints
[4, 5, 8, 9, 13]

Approved w/Constraints
[4, 5, 13, 14, 15]

3.6.x

Unapproved

3.7.x

Unapproved

3.8.x

Unapproved

Decision Constraints


[1]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[2]	Per the Initial Product Review: Apache James may not be used for any data containing Protected Health Information/Personally Identifiable Information (PHI/PII), or sensitive information; When using Simple Mail Transfer Protocol (SMTP) , Post Office Protocol (POP3), Internet Message Access Protocol (IMAP), Hypertext Transfer Protocol (HTTP) or other clear-text protocols, James should be configured to apply Secure Sockets Layer/Transport Layer Security encryption; System owners should disable insecure protocols and ports such as TELNET, and File Transfer Protocol; VA authorized enterprise mail solution is currently in place and should be leveraged. System owners should reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure proposed solution aligns with the VA enterprise architecture.

[3]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[4]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[5]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations.

[6]	Per the Initial Product Review: Apache James must not be used for any data containing Protected Health Information/Personally Identifiable Information (PHI/PII), or sensitive information; When using Simple Mail Transfer Protocol (SMTP) , Post Office Protocol (POP3), Internet Message Access Protocol (IMAP), Hypertext Transfer Protocol (HTTP) or other clear-text protocols, James must be configured to apply Secure Sockets Layer/Transport Layer Security encryption; System owners must disable insecure protocols and ports such as TELNET, and File Transfer Protocol; VA authorized enterprise mail solution is currently in place and must be leveraged. System owners must reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure proposed solution aligns with the VA enterprise architecture.

[7]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[8]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[9]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[10]	Per the Initial Product Review: Apache James must not be used for any data containing Protected Health Information/Personally Identifiable Information (PHI/PII), or sensitive information; When using Simple Mail Transfer Protocol (SMTP), Post Office Protocol (POP3), Internet Message Access Protocol (IMAP), Hypertext Transfer Protocol (HTTP) or other clear-text protocols, James must be configured to apply Secure Sockets Layer/Transport Layer Security encryption; System owners must disable insecure protocols and ports such as TELNET, and File Transfer Protocol; VA authorized enterprise mail solution is currently in place and must be leveraged. System owners must reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure proposed solution aligns with the VA enterprise architecture.

[11]	This technology must not be used for any data containing Personal Health Information/Personal Identification Information (PHI/PII), or sensitive information. When using Simple Mail Transfer Protocol (SMTP), Post Office Protocol 3 (POP3), Internet Message Access Protocol (IMAP), Hypertext Transfer Protocol (HTTP) or other clear-text protocols, this technology must be configured to apply Secure Sockets Layer (SSL)/ Transport Layer Security (TLS) encryption. System owners must disable insecure protocols and ports such as TELNET,and File Transfer Protocol (FTP). VA authorized enterprise mail solution is currently in place and must be leveraged. System owners must reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure proposed solution aligns with the VA enterprise architecture.

[12]	This technology must not be used for any data containing Protected Health Information/Personally Identifiable Information (PHI/PII), or sensitive data. When using Simple Mail Transfer Protocol (SMTP), Post Office Protocol 3 (POP3), Internet Message Access Protocol (IMAP), Hypertext Transfer Protocol (HTTP), or other clear-text protocols, this technology must be configured to apply Transport Layer Security (TLS) encryption. System owners must disable insecure protocols and ports such as TELNET and File Transfer Protocol (FTP). A VA authorized enterprise mail solution is currently in place and must be leveraged. System owners must reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure a proposed solution aligns with VA enterprise architecture.

[13]	This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle. Per the Initial Product Review, users must abide by the following constraints: Apache JAMES should not be used for any data containing Personal Health Information/Personal Identification Information (PHI/PII), or sensitive information. When using SMTP, POP3, IMAP, HTTP or other clear-text protocols, JAMES should be configured to apply SSL/TLS encryption. System owners should disable insecure protocols and ports such as TELNET, and FTP. VA authorized enterprise mail solution is currently in place and should be leveraged. System owners should reach out to Architecture, Strategy, and Design (ASD) for guidance on mail system implementation to ensure the proposed solution aligns with the VA enterprise architecture.

[14]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[15]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

Note:

At the time of writing, version 3.8.1 is the most current version, released 02/11/2024.

Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Name	Description
No components have been identified for this entry.


Collaboration and Electronic Workplace Collaboration Software	E-mail and Calendaring

General Analysis

Adoption Benefits

This technology can be acquired without cost through open source licensing and supports VA`s open source initiative.
This technology may create efficiencies for those with coding and development responsibilities.
This technology has a comprehensive set of documentation.

Adoption Risks

Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
The product is not Federal Information Processing standards (FIPS) 140-2 (or its successor) certified and has the potential to collect, store, or transmit Personally Identifiable Information (PII) or Protected Health information (PHI).
The product has several vulnerabilities noted in the National Vulnerability Database.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search/ for more details.
An enterprise license has already been acquired for a comparable technology.
This technology has the potential to collect, store, or transmit Personally Identifiable Information (PII)/Protected Health Information (PHI), and/or other sensitive VA data.
This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.
This technology can be used with Apache Cassandra, an unapproved technology.
This technology can be used with Open Java Development Kit (OpenJDK), an unapproved technology.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.
This technology can potentially use File Transfer Protocol (FTP), an unapproved protocol.
This technology can potentially use TELNET, an unapproved protocol.
This technology can integrate with and alter database technologies.
This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms.

Architectural Benefits

This technology can use a VA-preferred database.
This technology is portable as it runs on multiple TRM-authorized operating systems.

Architectural Risks

Apache James is not the standard VA enterprise mail solution.

- The information contained on this page is accurate as of the Decision Date (03/27/2024 at 02:56:36 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (03/19/2024)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (03/19/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework