Scan to email keeps working when the Exchange Server goes
The multifunction printer on the third floor was set up years ago, with a hostname, a port and a login nobody wants to touch. Point that hostname at Sendman and the printer keeps sending, while a policy decides which address it may send as.
EHLO mfp-3f-canon.contoso.local250 AUTH LOGIN PLAIN NTLMAUTH NTLM TlRMTVNTUAABAAAAB4IIog…235 Authentication successful. Let's send some emails!MAIL FROM:<scan@contoso.com>250 2.1.0 Sender OKRCPT TO:<accounting@contoso.com>250 2.1.5 Recipient OK
The printer keeps its login
Most printers and scanners can do one thing with email: open SMTP, maybe sign in, maybe switch to TLS, and send a PDF. Almost none can do OAuth, many cannot do TLS at all, and some only speak NTLM. That is why the last Exchange Server is still running.
With Sendman a printer that signs in with an Entra ID account keeps it, one with a domain login such as CONTOSO\svc-scan keeps that, and a printer that speaks NTLM gets a vault credential with the name it already uses. You repoint the hostname in DNS. A printer that sends with TLS on 587 or 465 keeps its port; one that only speaks plain SMTP keeps port 25 and sends through LNC, the Sendman tunnel.
Printers without TLS send through LNC
Sendman accepts a sign-in only once the session is encrypted, on every port but 25. A printer that cannot do TLS keeps port 25 and sends through LNC, the Sendman tunnel, signs in there and is held to the same policies. That port is not open to the internet; from Sendman onwards the session is encrypted wherever your backend supports it.
[ connected through LNC, the Sendman tunnel ]EHLO scanner-wh-02250-STARTTLS250 AUTH LOGIN PLAIN NTLMAUTH PLAIN AENPTlRPU09cc3ZjLXNjYW4A••••••••235 Authentication successful. Let's send some emails!
The printer may send as scan@, not as your CEO
A policy for the printer's login or its address range names the senders it may use, such as scan@contoso.com, and the recipients, such as your own domain. Anything else is refused in the SMTP conversation, and the printer's log shows the reason.
- Printers without a login field send from the address range of their site, still only as the senders the policy names.
MAIL FROM:<ceo@contoso.com>550 5.7.60 Sender address rejected: not authorized. No cookies no email.
Move the printers before the server goes
- Let the printers inLet the printers inAdd the address ranges of your sites to the allow list, and give the printers that should not carry a directory identity a vault credential.
- Say what each printer may doSay what each printer may doWrite a policy per printer or per site: which sender it may use, and to whom it may send.
- Repoint the hostnameRepoint the hostnamePoint the hostname the printers send to at Sendman. Watch the first scans arrive, then switch off the receive connector.
Questions about printers and scanners
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.
03Can a printer keep its NTLM login?
Yes, with a vault credential. NTLM works against the Sendman credential vault, not against Entra ID, so the printer gets a vault credential with the user name it already sends, and the password you set there.
04Can a device keep the user name it has today?
Yes. A vault credential can carry the name the device already uses, CONTOSO\svc-scan included, and an Entra ID account signs in with its user principal name or, if it is synced from Active Directory, with its domain login.