Overview
The error indicates that Send Email Action has failed to connect to SMTP server, or failed to send data using TLS or SSL protocol.
Event examples
See some examples of the TLS failed Event messages:
- TLS failed. The client and server cannot communicate, because they do not possess a common algorithm · 0x80090331.
- The certificate chain was issued by an authority that is not trusted · 0x80090325.
- The credentials supplied to the package were not recognized · 0x8009030D.
- The target principal name is incorrect · 0x80090322.
- The message received was unexpected or badly formatted · 0x80090326.
Cause
These errors typically occur when Automation Workshop cannot establish a secure communication channel (TLS or SSL) with the SMTP server. Possible reasons include network disruptions that interrupt data transmission mid-session, or the SMTP server not supporting the requested TLS or SSL protocols.
In some cases, the SMTP server might only support outdated encryption methods, resulting in compatibility issues.
Solution
The error message often provides a clue as to why the connection failed. Verify that your SMTP server supports the TLS version configured in your email settings (Action or Options). If you are uncertain, select automatic TLS version detection to ensure the correct protocol is used.
If you are working with self-signed certificates and encounter certificate authority is not trusted errors, you may opt to ignore TLS errors in the settings. Doing so allows connecting to your SMTP server using an encrypted channel.
Ignoring TLS errors is advisable only when operating over secure internal networks such as LAN or VPN. Additionally, consider updating or replacing outdated certificates and ensuring the server's supported algorithms match those set in your Tasks settings.
Older Windows operating systems may lack support for newer TLS protocols and modern cipher suites. In such cases, updating Windows to a more recent release that includes these protocols is beneficial.
It can also help to review and modify Windows system settings or Registry entries to ensure that required protocols (for example, TLS 1.2 or TLS 1.3) and related cipher suites are enabled. This can often restore compatibility and resolve credentials not recognized TLS errors.
Assistance is here…
If you have any questions, please do not hesitate to contact our support team.