> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/glpi-12/setup/authentication/imap.md).

# Authenticate from IMAP

The interfacing of GLPI with mail servers as a source of authentication.

This authentication source is configured from the menu `Setup > Authentication > Mail servers`.

This ability can compensate for the absence of directory or of CAS server. However, contrary to what is possible with other sources of other authentication sources, no mass import is available. A user is authenticated by GLPI if the server of mail server has authenticated him beforehand.

The connection to the mail server uses the IMAP or POP protocols. The options of SSL and TLS encryption are available. The distinction is made between the mail domain which is the part of the of the mail address that follows the asterisk character, and the fully qualified name of the mail server, which can serve several mail domains.


---

# 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://help.glpi-project.org/glpi-12/setup/authentication/imap.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.
