/
Change notice for TLS and port requirements in the Email functions

Change notice for TLS and port requirements in the Email functions

    We are changing how the Email notification and Email attachment functions connect to your SMTP server, so that outbound email can no longer leave UsageCloud unencrypted. Ports 465 and 587 will each get a fixed TLS mode, and port 25 will no longer be supported.

    What is changing

    • Port 465 will always use implicit TLS.

    • Port 587 will always use STARTTLS.

    • Port 25 will no longer be supported.

    • Encryption will always be enforced. If your SMTP server does not support the expected TLS mode for the port you configured, the stream will fail with an error. There will be no fallback to an unencrypted connection.

    • The TLS only checkbox will be removed from both functions, and there will no longer be any TLS setting to configure.

    Why we are making this change

    Currently you can deselect the TLS only checkbox, and the connection then uses TLS only if your server supports STARTTLS. That makes it possible for an email to go out unencrypted without you noticing. Fixing the TLS mode to the port removes that ambiguity, so you always know how a given port behaves.

    What this means for you

    • If your SMTP server supports TLS on the port you configured, your streams will then keep running as they are. You do not need to do anything.

    • If your SMTP server does not support TLS on that port, your streams will fail once the change takes effect. Your server must support TLS.

    • If you use port 25, you need to switch to port 465 or port 587.

    What you need to do

    1. Check which port each Email notification and Email attachment function in your streams uses.

    2. If a function uses port 25, change it to port 465 or port 587.

    3. Confirm that your SMTP server supports implicit TLS on port 465, or STARTTLS on port 587, depending on which one you use.

    4. If your server does not support TLS on that port, enable it on the server, or move to a provider that does.

    For more information, see Email notification and Email attachment.

    When this happens

    We expect to roll out these changes in phases from August 2026. Because the rollout is phased, the port change and the TLS enforcement may not reach your account at the same time. We recommend making the changes above before the rollout starts, so your streams are ready either way.

    If you have questions or need clarification, please do not hesitate to reach out to us through our Digitalroute Self-Service portal.