Skip to main content
CONNECTIONS AND TLS

Devices connect the way they already know

Sendman answers on port 587 with STARTTLS and on port 465 with implicit TLS, and a device signs in only once the session is encrypted. A device keeps its hostname and its login, and one DNS record points it at the relay; a device that only speaks plain SMTP sends on port 25 through LNC, the Sendman tunnel.

  • STARTTLS on port 587
  • Implicit TLS on port 465
  • Messages up to 25 MB
mfp-3f-canon.contoso.local → Sendmanport 587
220 ESMTP Service readyEHLO mfp-3f-canon.contoso.local250-SIZE 26214400250-8BITMIME250-SMTPUTF8250-ENHANCEDSTATUSCODES250-DSN250 STARTTLS

Port 587 with STARTTLS, port 465 with implicit TLS

Most devices send on port 587: they open a plain connection and switch to TLS with STARTTLS before they sign in. Devices set up for SMTPS use port 465, where TLS starts with the first byte. Both reach the same relay, the same sign-in and the same policies. Port 25 is not open to the internet: a device that only speaks plain SMTP sends there through LNC, the Sendman tunnel.

The ports Sendman answers on
PortTLSWho uses it
587STARTTLS, before the sign-inMost printers, scanners and applications
465Implicit TLS from the first byteDevices set up for SMTPS

A device without TLS sends through LNC

Many scanners and alarm panels never learned TLS, or offer only versions nobody accepts any more. Over the internet they cannot sign in: on port 587 Sendman offers the sign-in only after STARTTLS, and a login before it gets 538 5.7.11. They send on port 25 through LNC, the Sendman tunnel, the one port where a device may sign in without TLS, and the allow list, the sign-in and the policies apply there exactly as they do to an encrypted session.

Port 25 is not open to the internet. From Sendman to your backend the session is encrypted wherever the backend supports it.

alarm-panel-01 → Sendmanport 25 · LNC
[ connected through LNC, the Sendman tunnel ]EHLO alarm-panel-01250-STARTTLS250 AUTH LOGIN PLAIN NTLMAUTH LOGIN334 VXNlcm5hbWU6YWxhcm0tcGFuZWwtMDE=334 UGFzc3dvcmQ6••••••••235 Authentication successful. Let's send some emails!

Certificate, extensions and message size

  • The certificate renews without a restart

    Sendman presents the certificate of its platform on both ports and picks up a renewed one within a minute, so a renewal needs no change window.

  • Extensions the relay offers

    SIZE, 8BITMIME, SMTPUTF8, ENHANCEDSTATUSCODES, DSN when your backend offers them, plus STARTTLS, and AUTH once the session is encrypted. PIPELINING and CHUNKING are not offered, and an SMTP client only uses them when the server offers them.

  • Messages up to 25 MB

    Sendman says so in its EHLO reply. When your backend accepts less, its limit wins.

Every refusal tells the device which check stopped it

When Sendman decides something, the device gets the relay's own reply. Every other reply comes from your backend, as your backend wrote it.

The replies of the relay
ReplyWhen
235 Authentication successful. Let's send some emails!The sign-in worked.
535 Authentication failed. Please try again.The user name or the password is wrong.
550 5.7.60 Sender address rejected: not authorized. No cookies no email.No policy lets this identity send as this address.
550 5.7.1: Recipient not authorized, your account is not permitted to send to this addressA policy allows the sender, not this recipient. The other recipients still get the message.
421 service not availableSendman cannot read its configuration. A device that behaves holds the message and tries again.
No reply, the connection closesThe device's address is in no range of the allow list.

On port 465 a device whose configuration cannot be read gets no reply either: TLS comes first there, so the connection closes.

Questions about connections

01Which devices need LNC?

Only the ones that cannot do TLS. A device that speaks implicit TLS on port 465 or STARTTLS on port 587 reaches Sendman over the internet, and repointing its hostname in DNS is all it takes. A device that only speaks plain SMTP on port 25 needs LNC, the Sendman tunnel: that port is not open to the internet, and every other port refuses a login before TLS. The SMTP settings of each device tell you which side of the line it is on.

02What if a device cannot do TLS at all?

It sends through LNC, the Sendman tunnel, on port 25. That port is not open to the internet, and it is the only one where a device may log in without TLS; identity, IP and policy are enforced there in exactly the same way. From Sendman onwards, the session is encrypted wherever the backend supports it.

03How large can a message be?

Up to 25 MB. Sendman tells the device so in its EHLO reply, and when your backend accepts less, its limit wins.

Request a preview and point one scanner at Sendman.