> 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/admin-portal/insights/logs.md).

# Logs

The **Logs** dashboard lists the log entries of all connections to your Sendman instance. It is the first place to look when a message does not arrive.

## What you find in the logs

For each connection, the logs show among other things:

* the client's IP address and the port it connected to,
* whether the connection was refused because the address is not on the [IP Allow List](/admin-portal/sendman/ip-allow-list.md),
* the TLS handshake, including the TLS versions and cipher suites the client offered when the handshake fails,
* the sign-in result and the authenticated username,
* the sender and recipient addresses, and whether an [authorization policy](/admin-portal/sendman/authorization-policies.md) allowed them,
* the replies of your [SMTP backend](/admin-portal/settings/smtp-backend.md).

{% hint style="info" %}
Logs never contain passwords or other credentials.
{% endhint %}

## Searching

Enter a search term in the search bar to narrow down the entries, for example:

* the client's IP address, e.g. `192.0.2.10`, to follow a single device,
* a sender or recipient address, to follow a single message,
* a username, to check the sign-ins of a credential.

Narrow the time filter to the moment the problem occurred to keep the result small. The meaning of the SMTP replies is explained in [SMTP Reply Codes](/other/troubleshooting/smtp-reply-codes.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/admin-portal/insights/logs.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.