All mail Cyberdise sends is now handed over an encrypted connection whenever the receiving mail server offers one. This covers both campaign messages and system messages such as portal invitations, password resets and notifications.
How it works
Cyberdise uses opportunistic TLS:
- The sending server offers
STARTTLSto the receiving server. - If the receiver supports it, the session is encrypted and the message is delivered over TLS.
- If the receiver does not support it, the message is delivered in plain text as before.
This protects mail in transit without breaking delivery to the servers in your recipient base that have no TLS support. Existing mail flow is unchanged — nothing that was delivered before stops being delivered.
What you need to do
Nothing. The behaviour is on by default after the update and applies to every configured sender, including the per-sender mail configurations created for individual sending domains.
Verifying that TLS is in use
Send a test message to a mailbox you control and inspect the Received: header on the receiving side. A TLS-protected hop names the protocol and cipher, for example:
Received: from mail.example.com ...
(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384)The delivery log of the message (Schedule → Display Message Log) shows the same hand-off from the sending side.
Limitations
- Opportunistic TLS does not guarantee encryption. A receiver that offers no
STARTTLS still gets the message unencrypted, by design — the alternative would be to stop delivering to it.
- It does not authenticate the receiving server. If a recipient domain requires
enforced, authenticated TLS, that has to be arranged with that domain specifically.
Comments
0 comments
Article is closed for comments.