> For the complete documentation index, see [llms.txt](https://docs.sendman.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sendman.com/configuration/get-started/scenario-based-guides/printers-and-scanners.md). # Printers & Scanners Send scan-to-mail and notifications from multifunction devices through Sendman Multifunction printers and scanners often have limited SMTP support: no modern authentication, old TLS implementations, or port 25 only. This guide helps you choose the right settings for such devices. ## Choose the connection type | Device capability | Recommended setup | | ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | Supports STARTTLS or SSL/TLS and SMTP authentication | Connect over the internet on port `587` (STARTTLS) or `465` (SSL/TLS) with a [Sendman credential](/admin-portal/sendman/smtp-credentials.md). | | Supports TLS, but the handshake fails | Switch on [legacy TLS cipher suites](/admin-portal/settings/smtp-client.md) and try again. | | Only port 25, no TLS, or no authentication | Connect the device's network through a [network connection](/admin-portal/settings/network-connections.md) and send on port `25`. | ## Device settings | Setting | Value | | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SMTP server | `YOURNAME.sendman.com`. Over a network connection, use Sendman's tunnel address of that connection, e.g. `169.254.100.5` (see [Address plan](/admin-portal/settings/network-connections.md#address-plan)). | | Port | `587` (STARTTLS), `465` (SSL/TLS), or `25` (network connection only) | | Authentication | AUTH LOGIN, AUTH PLAIN or AUTH NTLM with a Sendman credential, or no authentication (see below) | | Sender address | An address that is listed as allowed sender in your [authorization policy](/admin-portal/sendman/authorization-policies.md) | | Maximum size | 25 MB per message. Reduce the scan resolution or split large scans if needed. | {% hint style="warning" %} On ports 587 and 465, Sendman only accepts authentication over an encrypted connection. A device that tries to sign in without TLS receives `538 Encryption required`. On port 25 over a network connection, authentication without TLS is allowed. {% endhint %} {% hint style="info" %} AUTH NTLM is supported with [Sendman credentials](/admin-portal/sendman/smtp-credentials.md) only. If your device signs in with NTLM, do not use an Entra ID account for it. {% endhint %} ## Devices without authentication Devices that cannot sign in can send anonymously, provided that: 1. They connect from a network on your [IP Allow List](/admin-portal/sendman/ip-allow-list.md), and 2. an [authorization policy](/admin-portal/sendman/authorization-policies.md) exists that * has **no username**, only an IP range (at most 16,384 addresses) that covers the device, and * has **Allow anonymous sending** switched on. Keep the IP range of such a policy as small as possible, ideally the device's own address, and restrict the allowed senders and receivers. {% hint style="info" %} For anonymous sending, Sendman must see the device's real address. Over the internet, this is the public address of your internet connection, which all devices behind it share. Over a [network connection](/admin-portal/settings/network-connections.md), Sendman sees the device's local IP address, so you can allow individual devices. {% endhint %} ## TLS handshake fails Some older devices only offer cipher suites that Sendman does not accept by default. The device then reports a TLS or SSL error, and the connection appears in [Logs](/admin-portal/insights/logs.md) as a failed TLS handshake. 1. First, check for a firmware update for the device. 2. If none is available, go to **Settings → SMTP Client** and switch on **Allow legacy TLS cipher suites**. See [SMTP Client](/admin-portal/settings/smtp-client.md) for the security implications. 3. If the device does not support TLS 1.2 at all, connect it through a [network connection](/admin-portal/settings/network-connections.md) and send on port 25 without TLS. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sendman.com/configuration/get-started/scenario-based-guides/printers-and-scanners.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.