SMTPS problem with v21 SP9HF1

[Thomas Steckbauer]

Hi,

any idea if SMTPS should also work with login credentials (login object defined via SMTP_LOGIN) or only with an email server's certificate as described in Setting up Secure Emails

We have tried port 25, 567 (both should work) and various SMTP_PROTOCOL settings in UC_CLIENT_SETTINGS, but always following errors are logged:

2024-03-07 07:54:06 - U00020408 0000000000050027

2024-03-07 07:54:06 - U00020408 535 TLS required|smtp.xxx.xxx

2024-03-07 07:54:06 - U00020408 U00050027 Authentication error '535 TLS required' (SMTP server: 'smtp.xxx.xxx')

Credentials seem to be fine as our mail provider receives a specific TLS error for the source and not an "incorrect password" message.

BR
Thomas

Automic		remove preview
Setting up Secure Emails As a system administrator, you can use the Automation Engine to send secure emails by using SMTPS. You can decide whether you configure one standard SMTP server, several ones (UC_SMTP_ MYSERVER1, UC_SMTP_ MYSERVER2, for example). SMTPS allows you to use TLS to secure the SMTP connection. View this on Automic >

[Thomas Steckbauer]

Seems that there were some improvements in version 21.0.10HF1 :-)

Finally we managed to send secure mails (SMTPS) now with SMTP_PROTOCOL=STARTTLS and and valid credentials defined with the SMTP_LOGIN variable :-))

Btw, have also asked the support to update the documentation to avoid any misunderstandings, as "Using TLS to secure the SMTP connection requires a certificate" is definitely not correct

[Frantisek Elias]

Hello Thomas,

we are also planning to set up secure emails on version 21.0.8hf1, did you find any bug which was fixed in version 21.0.10? How do you mean that certificate is not needed, you just ignored parameter SMTPS_ CERT in client vara? Thank you for your answer.

[Thomas Steckbauer]

Hi, I was just told by the support that a bug has been fixed with sp10 but not exactly which one. We are using (and have to use ) basic authentication do send secure mails, certificates are not supported from our mailhub. 

As mentioned above we just had to add following parameters to send secure mails from the AutomationEngine to the mailhub:

SMTP_LOGIN = (name of login object with credentials for the SMTP user)

SMTP_PROTOCOL = STARTTLS

Just to be sure, I'm not talking about end to end encryption of mails ;-)

In the documentation it is currently mentioned that secure mails can only be sent when using certificates, but it luckily also works now with basic authentication