> 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/documentation/modules/administration/mailqueue.md).
# Notification queue
All notification emails go through a queue before actual delivery. This allows keeping a history and a list of the various emails sent.
An automatic action (`queuedmail`) allows the sending of pending emails (see [Configure automatic actions](/documentation/modules/configuration/crontasks.md)). Another automatic action (`queuemailclean`) cleans the queue by keeping only recent emails.
The delay applied for sending notifications can be defined at entity level, see [administration by entity](/documentation/modules/administration/entities.md)). This allows for example in the case of rapid multiple modifications of an object to send only one notification.
{% hint style="warning" %}
using the queue does not work for a change, problem or ticket itself, only for a sub-object. For example, when changing the impact of a ticket, the email will be sent immediately; on the other hand, in the event of addition or modification of a follow-up, a task, a validation request... the email will be placed in the queue.
{% endhint %}
Example of queue
In the example above, the deadline for sending email notifications has been set to 20 minutes in the configuration of the entity; as a consequence the sending date is set at 20 minutes after the creation date.
Once the notification has been sent, the queue is placed in the recycle bin with the date sent.
{% hint style="info" %}
there will be as many queues in the recycle bin as there are recipients, each with its own sending date.
{% endhint %}
---
# 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/documentation/modules/administration/mailqueue.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.
