Knowledge base

security verifiedimportant

TLS mode towards the receiver

How hard the engine tries to encrypt: never, opportunistically, required, or required with strict certificate checks.

In detail

Four positions, from Never — use plain SMTP through Opportunistic (STARTTLS when offered), Encrypted (STARTTLS required, any certificate accepted) to Secured (STARTTLS with strict cipher and certificate checks). The middle position is where almost all bulk mail lives: encrypt when the receiver allows, never refuse to deliver over it. The strict positions turn a receiver's expired certificate into undelivered mail, which is a policy decision a customer should make knowingly — and one their recipients cannot see. The Not secure counter in the console counts deliveries that went unencrypted where the setting would have allowed encryption, which is the measurement to look at before tightening this.

What happens if you get it wrong

Set to a strict mode across all destinations.Every receiver with an expired or mismatched certificate stops receiving mail, and the failure names TLS rather than anything the recipient could act on.inference · inference