SLM SMTP Configuration Guide
SLM SMTP configuration enables Safety Lifecycle Manager to send email from the application. The required SMTP settings are stored within the application’s .env configuration file and define how SLM connects to the selected email provider.
Administrators can configure the SMTP host, user credentials, port, encryption method, authentication and TLS settings according to the requirements of the organization’s email environment.
This guide explains the SLM SMTP configuration variables demonstrated in the training and how each setting contributes to outbound email connectivity.
Understanding SLM SMTP Configuration
SMTP, or Simple Mail Transfer Protocol, provides the email delivery configuration used by SLM when the application needs to send email.
The SLM SMTP configuration is stored within the application’s .env file. This file can be found within the installed SLM code base and edited using a suitable text editor.
The training demonstrates a dedicated SMTP variable section containing the settings required to connect SLM to the organization’s SMTP provider.
Because the appropriate values depend on the email service being used, administrators should obtain the required server, authentication, port and encryption information for their own SMTP environment rather than copying example settings from another installation.
Locating the SMTP Settings in SLM
The SMTP variables are configured within the SLM .env file located in the application’s installation folder.
The training demonstrates opening this file with a text editor and locating the section containing the SMTP configuration variables.
The configuration includes settings covering:
- SMTP host
- SMTP user
- SMTP password
- SMTP port
- SMTP encryption
- SMTP authentication
- SMTP TLS
These values work together to define how SLM establishes the connection used for application email.
The SLM On-Premise Hardware and Software Requirements guide provides additional context for the wider infrastructure supporting an on-premise SLM deployment.
SMTP Host, User and Password Settings
Three of the principal SLM SMTP configuration variables identify the email provider and, where required, authenticate the connection.
SMTP_HOST identifies the hostname of the SMTP provider used by the SLM environment.
SMTP_USER contains the username used for SMTP authentication, while SMTP_PASS contains the associated password.
The training explains that the username and password can remain empty when the email provider does not require authentication.
Where authentication is required, the credentials configured for the SLM environment should correspond to the account and authentication method approved for the organization’s email infrastructure.
Configuring SMTP Port and Encryption
The SMTP port determines the network port used when SLM connects to the configured SMTP service.
The appropriate port depends on the email provider and its required connection configuration. Administrators should therefore use the port specified for their organization’s SMTP service.
The SMTP crypto setting defines the encryption method used for the connection. The training identifies SSL and TLS as available encryption options within the demonstrated configuration.
If the environment does not use the corresponding encrypted or authenticated configuration, the applicable settings can be left blank or disabled as demonstrated in the training.
Authentication and TLS Settings
The SLM SMTP configuration also contains settings that determine whether SMTP authentication and TLS are enabled.
The SMTP_AUTH setting is used to indicate whether username and password authentication is configured. The training demonstrates setting this value to 1 when authentication is enabled and 0 when it is not.
The SMTP TLS setting follows a similar approach. When TLS is being used for the SMTP encryption configuration, the training demonstrates enabling this setting with a value of 1. Otherwise, it is set to 0.
These settings should be configured consistently with the SMTP host, credentials, port and encryption requirements supplied by the organization’s email provider.
SLM SMTP Configuration Variables
The variables demonstrated in the SLM training can be summarized as follows:
SMTP_HOST– hostname of the SMTP provider.SMTP_USER– username used for SMTP authentication.SMTP_PASS– password associated with the SMTP user.SMTP_PORT– port number used for the SMTP connection.SMTP_CRYPTO– encryption method used for SMTP.SMTP_AUTH– enables or disables SMTP authentication.SMTP_TLS– enables or disables the demonstrated TLS configuration.
The exact values should be based on the SMTP service being connected to rather than treated as universal SLM defaults.
Securing the SLM Email Configuration
SMTP credentials can provide access to an organization’s email infrastructure, so the SLM configuration containing those credentials should be treated as security-sensitive.
Access to the application’s .env file should therefore be limited to administrators who require access to the SLM configuration.
When troubleshooting application email, administrators should also avoid exposing SMTP passwords when sharing configuration information, screenshots or log data.
Application-level troubleshooting may require information beyond the SMTP configuration itself. The SLM Application Maintenance Guide explains the IIS and PHP application logging available when investigating SLM behaviour.
Maintaining Reliable Application Email
SLM SMTP configuration provides the connection information the application requires to send email through the organization’s chosen SMTP provider.
A complete configuration requires the administrator to understand the SMTP host and port together with any authentication and encryption requirements imposed by that provider.
If authentication is required, the appropriate username, password and authentication setting must be configured. If TLS is required, the encryption and TLS settings must also reflect that requirement.
For general information about SMTP message transport, administrators can refer to the IETF Simple Mail Transfer Protocol specification. The SLM-specific variables and deployment configuration should continue to follow the MSS training and configuration supplied for the installed SLM environment.
