> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/releases/2025/1.168.0-30-july-2025.md). # 1.168.0 - 30 July 2025 ### Bulk Processing Updates Updates to our bulk processing for email activity and status events aim to reduce database interactions and streamlines operations, especially during large mailouts. This update eliminates redundant queues, simplifies status logic, and ensures complete event history. Key changes include accurate event records without inferred reads, immediate GNA marking for permanent failures, and treating 'AbuseReport' events as 'Opt-Out' requests. ### Improvements and Bug Fixes UbiQuity is constantly making small changes to ensure that behind the scenes everything will go as smoothly as possible and to continue to build a strong foundation to make improvements to the platform. * Improved host header verification now blocks access to non-service pages if the host header doesn't match the configured system host header, ensuring enhanced security. * Removed deprecated API v1 documentation link from the API page to prevent redirection to the dashboard. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ubiquity.co.nz/releases/2025/1.168.0-30-july-2025.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.