Overview
This article explains how to configure JetPatch to send emails through your organizational SMTP server.
Email functionality is required for password recovery and email alerts.
Configuration is performed by JetPatch administrators through the Settings menu.
Configuration Steps
To define an SMTP server:
- Make sure organizational firewalls allow the necessary traffic (usually TCP port 25 or 587) from the JetPatch Manager Console to the SMTP server.
- Log in as an Administrator.
- Go to Settings > Email and click Edit Configuration.
-
Configure the SMTP settings:
SMTP Settings
- Enable the configuration. If disabled, JetPatch will not send any emails of any kind.
- SMTP Host: DNS name of SMTP server.
- Domain Name: Enter the domain name from which to send emails.
- SMTP Port: Usually 25 or 587.
| Note: If using port 25, you may get a TLS error unless you disable TLS. Add the following property to intigua.properties and restart the service: |
| mail.smtp.starttls.enable=false |
- For versions before 5.0:
| /usr/share/tomcat/default/conf/intigua.properties |
- Post 5.0:
| /usr/share/intigua/services/data/intigua-main/conf/intigua.properties |
- Also, keep the domain, username, and password blank if using port 25.
- If you want to change the from address, add this property to intigua.properties:
|
mail.default.from.address=email@your_domain.com # dots in name are not supported, e.g. cannot use name.last.name@domain.com |
| Note: If you need to use port 465, see the Advanced Configuration section below. |
- Username: Enter the service account from which to send emails (required).
- Password: Enter the password of the service account (required).
| Note: If two-factor authentication is involved, you may need to use an app password instead of the account password. |
- If necessary, click Reset to clear the window fields and start again.
- Click Save.
To verify emails can be sent, click E-mail Alerts, enter an email address, click Send Test Email, and check your inbox.
Advanced Configuration (Port 465 or 587)
If you need to use port 465 or port 587 with SSL unchecked, navigate to the intigua.properties file:
For versions before 5.0:
| /usr/share/tomcat/default/conf/intigua.properties |
Post 5.0:
| /usr/share/intigua/services/data/intigua-main/conf/intigua.properties |
Add the following properties:
|
#use with port 465 or 587 SSL not checked mail.smtp.ssl.protocols=TLSv1.2
#use with port 465 SSL not checked mail.smtp.socketFactory.class=javax.net.ssl.SSLSocketFactory |
Troubleshooting
If sending a test email fails, check the manager logs (vmanage.log) for mail-related errors.
TLS Connection Errors (Port 25)
If logs show lines with SMTP, TLS, or errors such as "Could not convert socket to TLS" or "javax.mail.MessagingException", JetPatch is trying to start TLS on a port that does not support it.
Disable TLS by adding the following to intigua.properties and restarting the service:
| mail.smtp.starttls.enable=false |
Before 5.0:
systemctl restart tomcat
Post 5.0:
docker restart intigua-main
Then run Send Test Email again.
Port Connectivity Issues
If there are no TLS errors but the test still fails, verify connectivity from the JetPatch server to the SMTP server:
| nc -u smtp.yourcompany.com 587 |
- If it connects, the port is open. Check SMTP credentials or server settings.
- If it fails, the port is blocked, or the SMTP server is not listening on that port.
Comments
0 comments
Please sign in to leave a comment.