Sending email via SMTP failed

Ignition
,
1

One of our customers reached out today, saying that sending alarm emails no longer works (for the last few days).
When I try sending a test email from the Ignition gateway Test SMTP Server page, this is what I get back:

Valalta_SMTP_error2
Valalta_SMTP_error21304×176 9.05 KB

And this is in the logs:

ScriptDispatcher	30May2023 13:38:21	([default]Valalta/Alarmi/avg_kisik_bazen3, alarmActive) Error executing tag event script: Traceback (most recent call last): File "", line 2, in alarmActive File "", line 18, in sendAlarmEmail nested exception is: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2055) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:697) at javax.mail.Service.connect(Service.java:386) at javax.mail.Service.connect(Service.java:245) at javax.mail.Service.connect(Service.java:194) at javax.mail.Transport.send0(Transport.java:253) at javax.mail.Transport.send(Transport.java:124) at com.inductiveautomation.ignition.gateway.smtp.SmtpManagerImpl.sendMailWithRetries(SmtpManagerImpl.java:215) at com.inductiveautomation.ignition.gateway.smtp.SmtpManagerImpl.sendEmail(SmtpManagerImpl.java:181) at com.inductiveautomation.ignition.gateway.script.GatewayNetUtilities._sendEmail(GatewayNetUtilities.java:67) at com.inductiveautomation.ignition.common.script.builtin.AbstractNetUtilities.sendEmail(AbstractNetUtilities.java:149) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) javax.mail.MessagingException: javax.mail.MessagingException: Could not connect to SMTP host: mail.valalta.hr, port: 465; nested exception is: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)

What does that mean?
Can anybody shed some light...?

On the Ignition gateway, the configuration is not changed for the last 5 years.
To me, it seems that their IT has changed something regarding SMTP email sending...

And the Ignition version is:

ignition_version
ignition_version1231×455 40.8 KB

2

I had the same fault when gmail removed SMTP support from their free accounts.

It's on the email side of things.

3

Yes, I understand, but this is not Gmail...
This is the company's SMTP server.

4

They probably finally applied patches to close off access via the older, insecure TLS protocols. You will almost certainly have to upgrade to one of the last versions of v7.9.

5

If this is the case, it looks like TLS v1.2 support was added in 7.9.18.

6

OK then, upgrade it is... :upside_down_face:

7

I have the same issue and have not seen solution to it. My ignition ins hosted in the AWS cloud

image
image653×362 63.3 KB

8

Upgrade from 7.9.12?

Preferably to something that is supported and receiving security updates :grimacing:

9

There is a plan to upgrade in 8 months time, but presently, need to send report through email

10

The fix is to upgrade. Your choices are simple:

  1. Upgrade.

  2. Continue having emails blocked.

Do note that this topic is about enabling TLS1.2 to talk to "modern" email servers. TLS1.2 is already vulnerable and you may need to upgrade past Ignition v7.9 entirely (to get to TLS1.3) before your mail servers will accept anything. (Though supporting TLS1.2 for legacy apps is still a thing in some places.)