23 January 2026
TVC supports sending emails using SMTP authentication, which is required by most modern mail servers. By default, SMTP authentication is disabled. To enable it, set the global property tvc.core.mail.smtp.auth=true default value is false. When enabled, TVC sends emails using the configured SMTP credentials. When disabled, TVC sends emails without authentication, maintaining backward compatibility with existing configurations.
To enable SMTP authentication, define the following properties in the tvc.properties file:
| Property | Description | Default Value |
|---|---|---|
tvc.core.mail.smtp.host |
Specifies the SMTP server host name for sending emails, for example- |
|
tvc.core.mail.smtp.port |
Specifies the port number on which the SMTP server listens for email connections. Common values are |
25 |
tvc.core.mail.smtp.auth |
Enables or disables SMTP authentication. Set to |
false |
tvc.core.mail.smtp.auth.mechanism |
Specifies the authentication mechanism. Supported values are |
LOGIN |
tvc.core.mail.smtp.user |
Specifies the email address used to authenticate with the SMTP server when authentication is enabled. |
|
tvc.core.mail.smtp.password |
Specifies the password or OAuth2 Access Token (when mechanism is |
|
tvc.core.mail.smtp.starttls.enable |
Enables the use of the STARTTLS command to switch the connection to a TLS-protected connection. |
true |
tvc.core.mail.smtp.ssl.enable |
Enables the use of SSL/TLS on the initial connection (typically for port 465). |
false |
tvc.core.mail.debug |
Enables JavaMail protocol debug logging. Raw SMTP commands and server responses will be logged to stdout. |
false |
When these properties are configured, TVC will use them directly for SMTP authentication while sending emails.
Fallback Configuration via enovia.ini
If the SMTP properties are not defined in tvc.properties, TVC will automatically fall back to retrieving the configuration from the enovia.ini file using the following parameters:
| Property | Description | Default Value |
|---|---|---|
MX_SMTP_HOST |
Specifies the SMTP server host namefor sending emails, for example- |
|
MX_SMTP_PORT |
Specifies the port number on which the SMTP server listens for email connections. Common values are |
25 |
MX_SMTP_SENDER |
Specifies the email address used to authenticate with the SMTP server when authentication is enabled. |
|
MX_SMTP_PASSWORD |
Specifies the App password associated with the configured SMTP user. This value is used only when SMTP authentication is enabled. |
This ensures compatibility with existing Enovia-based configurations.
Important Note on SMTP Password Configuration
For the property tvc.core.mail.smtp.password and MX_SMTP_PASSWORD, an App Password or an OAuth2 Access Token (when the mechanism is set to XOAUTH2) must be used instead of the actual email account password. This is required for providers like Gmail or Microsoft 365 that enforce app-based or token-based authentication.
|
| Properties defined in tvc.properties take precedence over values configured in enovia.ini. |
Why an App Password Is Required?
Most modern email service providers (such as Gmail, Microsoft Outlook, and others) Do not allow direct authentication using the primary account password for third-party applications, Enforce enhanced security policies, including multi-factor authentication (MFA) Require a separate, application-specific password for non-interactive applications like TVC.
High-Level Steps to Generate an App Password:
Although the exact steps may vary depending on the email provider, the general process is as follows:
Log in to the email account used for sending emails.
Enable Two-Factor Authentication (2FA/MFA) for the account.
Navigate to the Security or Account Security section.
Generate a new App Password for an email or SMTP-based application.
Copy the generated App Password and configure it as the value for
tvc.core.mail.smtp.password in tvc.properties or MX_SMTP_PASSWORD in enovia.ini.
| The generated App Password is usually displayed only once. Make sure to store it securely. |
Why an OAuth2 Access Token Is Required?
OAuth2 is the modern industry standard for secure authorization. It provides several advantages over traditional password-based authentication:
Enhanced Security: Instead of using a permanent password, OAuth2 uses short-lived access tokens that expire automatically.
No Password Exposure: The application never handles or stores the user’s actual password.
Granular Access: Tokens can be restricted to specific actions (like sending email) without granting full account access.