TLS for email transport: protect SMTP connections in transit

TLS protects SMTP traffic while it crosses a network, but it is transport encryption—not end-to-end encryption of the message stored in a mailbox.

TLS encrypts the connection between two systems. For AuthSMTP customers that includes the connection used to submit mail and, where the receiving server supports it, the connection used for onward delivery.

Submission and delivery are different connections

  • Configure your application to use the secure settings supplied for the AuthSMTP account.
  • Validate certificates; do not disable verification to make an error disappear.
  • Keep the operating system and TLS library supported and patched.
  • Remember that ordinary SMTP delivery may be opportunistic unless a separate policy enforces TLS.
  • TLS does not encrypt a message once it is stored or displayed at either end.

See AuthSMTP SSL/TLS support and the relevant setup guide for your application. If the message itself must remain unreadable to intermediaries or mailbox operators, use a suitable end-to-end technology and key-management process.

Key takeaway
Use an encrypted AuthSMTP submission connection and avoid sending sensitive content that requires end-to-end protection as ordinary email.
Practical next step

Confirm that the application connects using TLS with certificate validation enabled, then inspect a received message's transport-security details.

Using AuthSMTP

AuthSMTP supports encrypted message submission and uses TLS for onward delivery when the receiving server offers it; select the supported secure port and keep certificate validation enabled.