> 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/readme.md).

# Sendman Documentation

Managed SMTP relay for printers, scanners, applications and devices

{% hint style="warning" %}
**Work in progress**\
\
Sendman and this documentation are still in **Private Preview**. Things may change along the way, and the occasional error might sneak in.

Found one? [Let us know!](https://products.glueckkanja.com/support/tickets/new?product=sendman) Your feedback helps us improve Sendman and its documentation.
{% endhint %}

Sendman is a managed SMTP relay delivered as a cloud service. Printers, scanners, line-of-business applications and other devices hand their mail to Sendman, and Sendman delivers it securely to the mail server of your choice, for example Exchange Online.

Sendman decides for every connection and every message whether it is allowed: which networks may connect, how clients authenticate, and which sender and recipient addresses they may use. You manage all of this in your own Sendman Admin Portal. No relay servers have to be operated on premises.

![](https://1641814212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EVg4twS3gtObqtkynsm%2Fuploads%2Fgit-blob-19f35e4de1d11af7fbb685a1b770e5c9746ebfcc%2Fsendman-flow.svg?alt=media)

These docs cover the configuration and use of Sendman. Start with the [Overview](/overview.md) or go straight to [Getting Started](/configuration/get-started.md).


---

# 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/readme.md?ask=<question>&goal=<user_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.