> 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/release-notes/2025/2025.19.0.md). # 2025.19.0 May 13, 2025 ### Mail in Daylite * Mail in Daylite is now available in Early Access, as we continue to add features and fixes. * You can try out Mail in Daylite today and help us improve it by sharing your feedback. * [Learn more](https://docs.daylite.app/learn/mail-management/early-access) about how to get started, a roadmap of features we are working on next, and an FAQ to answer some of the questions you may have. * Requires macOS 14 Sonoma or newer. ### Mail in Daylite Improvements and Fixes * Attachments in Mail in Daylite can now be saved to the Mac using the “Save Attachment” or “Save to Downloads Folder” context menu options. * The auto-complete list of participants in the New Message window in Mail in Daylite will now show Daylite users at the top of the search results. The results will now also show the default company name and the email address label. * Fixed an issue where Mail in Daylite was not correctly restoring the position of panes when returning to the My Mail view. ### Other Improvements and Fixes * Fixed a crash that could occur when deleting attachments. --- # 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/release-notes/2025/2025.19.0.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.