Applies to: Outbound SMTP customers whose mail client, application, or device connects using TLS 1.0 or TLS 1.1.


What is changing


On 9 December 2026, Outbound SMTP will stop supporting TLS 1.0 and TLS 1.1. After that date, our servers accept only TLS 1.2 and TLS 1.3.

  • This applies to STARTTLS connections on all Outbound ports: 25, 465, 587, and 2525.
  • TLS 1.0 and 1.1 have known security problems.
  • We are also removing anonymous cipher suites. These do not authenticate the server, so they do not protect your SMTP password.
  • Our hostnames and certificates do not change.


A mail client, application, or device that supports only TLS 1.0 or 1.1 will not be able to send email through Outbound after the change.

If your sender already uses TLS 1.2 or 1.3, nothing changes for you.

We are running scheduled tests before the permanent change. During a test, TLS 1.0 and 1.1 are switched off for a set period and then switched back on, so you can find problems early.


Date and time (UTC)Change
Tue 24 Nov 2026, 14:00-15:001-hour test, then TLS 1.0 and 1.1 are enabled again
Thu 26 Nov 2026, 14:00-18:004-hour test, then TLS 1.0 and 1.1 are enabled again
Tue 1 Dec 2026, 14:00-18:004-hour test, then TLS 1.0 and 1.1 are enabled again
Wed 9 Dec 2026, 14:00Permanent change

If the schedule changes, the most up-to-date information is on our status page: status.duocircle.com.


Do I need to do anything?

You may be affected if your sender is one of these:

  • Windows Server 2008 R2 or older, or Windows 7 or older
  • An application built on .NET Framework 4.5 or older
  • An application that uses Java 7 or older, or OpenSSL 1.0.0 or older
  • A printer, scanner, or copier with old firmware

How to check

  1. Send a test message from the system through Outbound.
  2. Find the message in the Message Log Viewer at logs.duocircle.com and open its Text log.
  3. Look for the line <smtpd> STARTTLS enabled .... It must show TLSv1.2 or TLSv1.3.

If it shows TLSv1 or TLSv1.1, the sender will stop working on 9 December unless you act.


Your options

Option 1 (recommended): update the sender to use TLS 1.2 or later

Fixing the sender is the best long-term solution, because the whole connection stays encrypted with a current protocol.

  • Printers, scanners, copiers, and other devices: check the manufacturer's website for a firmware update that adds TLS 1.2 or later support.
  • Applications and scripts: update to the latest version, or check the documentation for a TLS or security protocol setting.
  • Operating system or runtime: if the sender depends on an old operating system or runtime (see the list above), it may need to be updated. Your IT team or the software vendor can advise.


Option 2: use a relay on your own network

If the sender cannot be updated or replaced, you can place a small mail relay or TLS proxy on your own infrastructure. The sender connects to the relay using the older protocol, and the relay connects to Outbound SMTP using TLS 1.2 or later.

One example of this type of product is Rebex TLS Proxy. Other products and approaches exist. This is an example only: DuoCircle does not endorse, support, or provide configuration help for third-party products.

Please consider:

  • The connection between your sender and the relay still uses the older, weaker protocol. Keep the relay on the same trusted network as the sender, not across the internet.
  • Your SMTP login credentials travel over that first connection, so protect that network accordingly.
  • You are responsible for installing, securing, and maintaining the relay.
  • This is a workaround. Updating or replacing the sender is the better long-term fix.


Option 3: replace the sender

If the sender cannot be updated and a relay is not practical, the remaining option is a replacement that supports TLS 1.2 or later.


Need help?

If you see TLS errors with Mailhop during or after these steps, contact support@duocircle.com. Tell us:

  • The time of the error
  • The server hostname
  • The port
  • The full error message