> 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/tutorials/fr/receivers/receiver_icloud.md).

# Collecteur iCloud

Si vous voulez collecter des emails depuis une boîte mail iCloud pour les transformer en tickets GLPI, voici les instructions.

* Compte iCloud
  * Votre compte iCloud doit avoir une adresse email dans le domaine icloud.com. L'Apple ID ne peut pas être utilisé, seulement l'adresse email.
  * Le mot de passe de votre compte iCloud ne fonctionnera pas. Vous devez générer un mot de passe d'application dans les paramètres de sécurité de votre compte iCloud. Pour cela, Apple fournit la documentation ici .
  * Apple fournit les paramètres de connexion IMAP ici .
* GLPI
  * Configurez le collecteur avec les paramètres de connexion IMAP fournis par Apple.
  * N'oubliez pas de saisir le **mot de passe d'application** et non le mot de passe du compte.

Trouvez la configuration générique d'un collecteur ici .


---

# 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/tutorials/fr/receivers/receiver_icloud.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.