Revist Email not working : Could not convert socket to TLS

Ignition
1

Email Alerts stopped and the wrapper logs says " Could not convert socket to TLS." Another user posted the same problem and the described fix according to Kevin sounds simple, but if you download the Alarm Module zip and extract it, there is no *.modl file to install the module using the gateway interface. Is there some magic way to install a module without the *.modl file?

[quote] Re: Notification email stopped working Could Not Convert SOCKET Topic is solved

This will be kinda weird, but go to the modules page and re-download just the 7.6.4 alarming module and install it… should fix your problem.

We had to release a hot fix but it’s not included in the installer.

Kevin Herron
Senior Software Developer
Inductive Automation [/quote]

2

That’s only going to work if you’re on 7.6.4.

And the zip thing - it’s likely because you’re using internet explorer and it has renamed the file for you. After you download the module, change the extension from .zip back to .modl.

3

Thanks Kevin for the fast reply, I am using 7.6.4 and I did download the file with internet explorer.

[quote=“Kevin.Herron”]That’s only going to work if you’re on 7.6.4.

And the zip thing - it’s likely because you’re using internet explorer and it has renamed the file for you. After you download the module, change the extension from .zip back to .modl.[/quote]

4

Hi, the patch did fix the “Could not convert socket to TLS” error, but now I get the following message:

550 5.7.1 Client does not have permissions to send as this sender
DEBUG SMTP: got response code 550, with response: 550 5.7.1 Client does not have permissions to send as this sender

Any idea of what I need to do to allow the client to send?

I’m a little confused as to why it’s broken. At one time the alerts worked without any issues.

5

Something may have changed with the SMTP server you’re using. Any error messages you see are coming from the server, not from Ignition. We just report the responses we get.

Is there an IT department you can verify both the username and the from address with?

6

Hi Kevin, I am the IT department. I haven’t made any recent changes to the exchange server ( that I remember). I have tried a few different accounts as the sender, as well as my own, but always get the same message returned. If you say the message is returned from my server, I will have a closer look at it. Thanks.

[quote=“Kevin.Herron”]Something may have changed with the SMTP server you’re using. Any error messages you see are coming from the server, not from Ignition. We just report the responses we get.

Is there an IT department you can verify both the username and the from address with?[/quote]

7

There’s an option under the advanced section you can enable on the email notification profile that turns debug logging on. This will log most of the back and forth between Ignition and the SMTP server.

These messages only go to the wrapper.log files, so you’ll have to look there for what’s happening rather than the console page on the gateway.

8

wrapper.log helps!

Resolved Email send error (wrapper.log):
550 5.7.1 Client does not have permissions to send as this sender
DEBUG SMTP: got response code 550, with response: 550 5.7.1 Client does not have permissions to send as this sender

  1. On the exchange server, open “Active Directory Users and Computers”, then open the properties for the user configured in the (ignition) Alarm Notification block.
  2. On the security tab, add the user that is configured in the “gateway notification Email settings” to the group/user name list.
  3. Select the added user in the list, scroll to find the “send As” permission and select “allow”.