> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/deutsch/e-mails/terminieren-von-e-mails-und-des-postausgangs.md).

# Terminieren von E-Mails

{% embed url="<https://enate.cdn.spotlightr.com/watch/MTM2MTY4Mw==>" %}

Sie können das Datum und die Uhrzeit für den Versand einer E-Mail planen, indem Sie die Option Senden planen auswählen.&#x20;

Die geplante E-Mail wird in den Ordnern " Mitteilungen" und "Zeitleiste" angezeigt, zusammen mit der Angabe, wer sie geplant hat und für wann sie geplant wurde. Sie können eine geplante E-Mail auch sofort über die Registerkarten " Mitteilungen" und "Zeitleiste" versenden.

![](https://gblobscdn.gitbook.com/assets%2F-MWYnDNwe3Cuo4zlGbs5%2F-MjUU4GA2Of4CwaPt8lV%2F-MjUX2xllVeXBSXeeD3G%2FSchedule-Send%20\(1\).gif?alt=media\&token=589f40f2-71d1-4d15-b29c-3f75bdc26724)

Note that you cannot schedule an email that exceeds the size set in Builder - see here for more information. However, validation of the email size occurs as part of saving the email, not at the sent time. So if a 25MB email has been scheduled and then the maximum email size gets reduced in Builder to 10MB, the scheduled email will still be sent as it conformed to the size allowance configured when it was scheduled.


---

# 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.enate.net/enate-help/deutsch/e-mails/terminieren-von-e-mails-und-des-postausgangs.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.
