> 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/other/changelog.md). # Changelog ## Private Preview Release - October 2026 * Managed SMTP relay with STARTTLS (port 587) and implicit TLS (port 465), TLS 1.2 and TLS 1.3 * Client authentication with Sendman credentials (AUTH LOGIN, PLAIN, NTLM) and Microsoft Entra ID accounts (AUTH LOGIN, PLAIN) * IP allow list and priority-based authorization policies for senders and recipients, including anonymous sending for devices * SMTP backend with STARTTLS, backend authentication and mutual TLS with a client certificate * Optional legacy TLS cipher suites for older printers and scanners * WireGuard and IPsec network connections with port 25 for local networks, and dedicated egress gateways with fixed IP addresses * Admin Portal with Insights dashboards, role-based access and API access tokens for the REST API --- # 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/other/changelog.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.