> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/center/install-uninstall-and-update/revert-to-the-legacy-daylite-mail-assistant-plugin.md).

# Revert to the Legacy Daylite Mail Assistant Plugin

In certain situations, you may need to revert to the Legacy Mail Assistant Plugin. To accomplish this, please follow the instructions outlined below.

{% hint style="warning" icon="box-archive" %}
**Archived:** This feature is no longer supported. This article remains available for reference but is no longer maintained.
{% endhint %}

### Turn off Daylite Mail Assistant Extension

1. Quit Daylite and Mail
2. Choose Apple menu () > **System Settings** > **Privacy & Security**
3. Scroll to the bottom of the Settings Window and Under **Other** choose **Extensions**
4. Click **Added Extensions**
5. Locate Daylite and turn off `com.apple.email.extension`

### Turn on Daylite Mail Assistant Plugin

1. Open Daylite.
2. Hold **Command (**⌘) and choose **Daylite** > **Install Mail Assistant.**
3. Open Mail.
4. Choose **Mail** > **Settings** > **General**.
5. Click **Manage Plugins**
6. Turn on **Daylite Mail Assistant**
7. Click **Apply and Restart Mail**
8. Quit Mail
9. Hold down the Option and open Mail


---

# 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.daylite.app/help/center/install-uninstall-and-update/revert-to-the-legacy-daylite-mail-assistant-plugin.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.