For JetPatch to be able to send emails (for password recovery, and for email alerts), you need to configure its connection to the organizational SMTP server.

To define an SMTP server:

• Make sure that 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:

  

  • Enable the configuration. If disabled, JetPatch will not send any emails of any kind.
  • SMTP Host: DNSname of SMTP server
  • Domain Name: Enter the domain name from which to send emails.
  • SMTP Port: Usually 25 or 587.
    • Note: if using 25, add the following property to intigua.properties and  restart  tomcat:
      • mail.smtp.starttls.enable=false
      • Also, keep domain, username, and password blank if using port 25
    • Note2: if you need to use port 465, see below
  • Username: Enter the service account from which you want to send an email (required) 
  • Password: Enter the password of the service account (required)
    • Note: if two-factor authentication is involved, you may need to use “apps password”
  • If necessary, you can Reset the window fields to start again.
  • Click Save.
• To check Emails can be sent Click on E-mail Alerts
• Enter the email ID and click on send a test e-mail and check your inbox 

Advanced Configuration (Port 465 or 587)

If you need to use a configuration like the below or with 587 with SSL unchecked

Then, you need to be running JetPatch 4.2.2.54 or above and add the following properties in intigua.properties (/usr/shar/tomcat/default/conf)

#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 the connection is failing, ssh into the JetPatch server and try to netcat (or telnet) to the SMTP server.  Example with port 587

netcat -u smtp.jetpatch.com 587

If the connection succeeds, a blank screen will show up, meaning that the port is open.

A failed connection will be accompanied by an error message. It can indicate either a closed port or the fact that the indicated remote server is not listening on the provided port.