> 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/2026/1.179.0-18-june-2026.md).

# 1.179.0 - 18 June 2026

### **Release Overview**

This release focuses on enhancing the reliability and scalability of the platform, with improvements to email delivery, rendering, and tracking.

We’ve also made some targeted updates to improve usability and visibility when managing templates and mailouts.

***

### **Email suppression handling**

We’ve removed reliance on the global AWS SES suppression list, improving how email suppression is managed within UbiQuity.

Email suppression is now handled entirely through UbiQuity's native GNA (Gone No Address) function. When a contact's email address receives a hard bounce, their GNA flag is automatically set to Yes and they are excluded from mailouts going forward. This gives you better control and consistency over which contacts are suppressed, and makes email delivery behaviour more predictable.

&#x20;For more information on how GNA works, see [GNA (Gone No Address)](https://docs.ubiquity.co.nz/documentation/audience-management/gna-gone-no-address).

***

### **Email Templates: Folder organisation**

You can now organise your email templates into folders, making it easier to manage and navigate large numbers of templates. All existing templates will be placed into a default folder after the release. You can then move templates into new or existing folders as needed to organise them by campaign, brand, or purpose.

This helps teams keep templates structured by improving efficiency when creating and updating mailouts.

<figure><img src="/files/UcbN0qfqPRdSy82ocpdS" alt=""><figcaption></figcaption></figure>

***

### **Mailout minimum send notification**

We’ve introduced an optional notification for automated mailouts that alerts you when a run sends to fewer contacts than a configured minimum threshold.

This helps identify potential issues with audience selection or filtering, ensuring automated mailouts are reaching the expected number of recipients.

<figure><img src="/files/Ijs49Kygtob1qyb27KRC" alt=""><figcaption></figcaption></figure>

***

### **General improvements**

We’ve made a number of behind-the-scenes improvements to the platform, including enhancements to:

* Email rendering consistency
* Email tracking and reporting reliability
* System performance and scalability
* Platform security and monitoring

These changes help ensure a more stable and consistent experience across UbiQuity.


---

# 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/2026/1.179.0-18-june-2026.md?ask=<question>&goal=<endgoal>
```

`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.
