# Sending email via SMTP failed **URL:** \ **Category:** Ignition\ **Tags:** ignition79, vision\ **Created:** [June 5, 2023, 12:39pm UTC](https://forum.inductiveautomation.com/t/sending-email-via-smtp-failed/74559 "2023-06-05T12:39:58Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\ **Post date:** [June 5, 2023, 12:39pm UTC](https://forum.inductiveautomation.com/t/sending-email-via-smtp-failed/74559/1 "2023-06-05T12:39:58Z")
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](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/2/b2483191e8b2c98fda581b4c240c4ef5bde1b0b4.png) And this is in the logs: ```auto 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](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/2/0205b1afccda4b539276290613a691403f7c3f1e.png) ---
**Author:** ![kyler.kamyszek](https://avatars.discourse-cdn.com/v4/letter/k/a4c791/32.png) [@kyler.kamyszek](https://forum.inductiveautomation.com/u/kyler.kamyszek)\ **Post date:** [June 5, 2023, 12:46pm UTC](https://forum.inductiveautomation.com/t/sending-email-via-smtp-failed/74559/2 "2023-06-05T12:46:00Z")
I had the same fault when gmail removed SMTP support from their free accounts. It's on the email side of things. ---
**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\ **Post date:** [June 5, 2023, 12:50pm UTC](https://forum.inductiveautomation.com/t/sending-email-via-smtp-failed/74559/3 "2023-06-05T12:50:38Z")
Yes, I understand, but this is not Gmail... This is the company's SMTP server. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 5, 2023, 12:55pm UTC](https://forum.inductiveautomation.com/t/sending-email-via-smtp-failed/74559/4 "2023-06-05T12:55:12Z")
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. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [June 5, 2023, 1:31pm UTC](https://forum.inductiveautomation.com/t/sending-email-via-smtp-failed/74559/5 "2023-06-05T13:31:18Z")
If this is the case, it looks like TLS v1.2 support was added in 7.9.18. ---
**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\ **Post date:** [June 5, 2023, 4:14pm UTC](https://forum.inductiveautomation.com/t/sending-email-via-smtp-failed/74559/6 "2023-06-05T16:14:58Z")
OK then, upgrade it is... 🙃 ---
**Author:** ![abiodun.martins1](https://avatars.discourse-cdn.com/v4/letter/a/f04885/32.png) [@abiodun.martins1](https://forum.inductiveautomation.com/u/abiodun.martins1)\ **Post date:** [July 21, 2026, 6:54pm UTC](https://forum.inductiveautomation.com/t/sending-email-via-smtp-failed/74559/7 "2026-07-21T18:54:54Z")
I have the same issue and have not seen solution to it. My ignition ins hosted in the AWS cloud ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/5/6511e9ccc98d2b538012e57de301f5971bfc2153.png) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 21, 2026, 7:04pm UTC](https://forum.inductiveautomation.com/t/sending-email-via-smtp-failed/74559/8 "2026-07-21T19:04:53Z")
> [@abiodun.martins1](#): > > I have the same issue and have not seen solution to it. > [@Kevin.Herron](#): > > If this is the case, it looks like TLS v1.2 support was added in 7.9.18. Upgrade from 7.9.12? Preferably to something that is supported and receiving security updates 😬 ---
**Author:** ![abiodun.martins1](https://avatars.discourse-cdn.com/v4/letter/a/f04885/32.png) [@abiodun.martins1](https://forum.inductiveautomation.com/u/abiodun.martins1)\ **Post date:** [July 21, 2026, 7:19pm UTC](https://forum.inductiveautomation.com/t/sending-email-via-smtp-failed/74559/9 "2026-07-21T19:19:05Z")
There is a plan to upgrade in 8 months time, but presently, need to send report through email ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 21, 2026, 7:27pm UTC](https://forum.inductiveautomation.com/t/sending-email-via-smtp-failed/74559/10 "2026-07-21T19:27:01Z")
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.)