> 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.165.0-19-march-2025.md).
# 1.165.0 - 19 March 2025
### Features
**New "Sent" status is being introduced for outbound email messages.**
Emails sent as part of mailouts or triggered emails will now have their status updated to "Sent" once they have been confirmed as being successfully sent by Amazon SES. In addition, the status of mailouts will remain in a "Sending" state until all messages in the mailout have been confirmed as sent.
You will note that there is no longer a Processed Status which has been superceeded by the Sent Status
Within a Contact history you will see the below information:
If you have any questions about the new Sent status please [reach out](mailto:support@ubiquity.co.nz?subject=RE%3A%20Senet%20email%20status%20-%201.165.0) to the team.
### Improvements and Bug Fixes
* In this release there has been some improved monitoring notifications to decrease the likelyhood of any issues not being caught early
* Security and compliance: HSTS header is now included in all HTTP responses:
* Fixed an issue where mailout links with tracking enabled would sometimes record two clicks for the same click event.
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.
### Update Release 1.165.1 - March 31st 2025
**Send at specific time options change**
When sending a mailout at a specific time, the default option will now be to "prepare the mailout at the time it is scheduled to send". This helps maintain the integrity of any opt outs and ensures that your data is up to date at the time of send.
You can change this to "prepare this mailout now" which will send to those that meet the filter criteria at the time you complete the mailout wizard.
**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
* In this patch release there are some minor improvements to the mailout dashboard updates. Updates received in the back end have not been reflected accurately in the front end in some cases.
### Update Release 1.165.3 - April 15th 2025
This update to release 1.165.0 will be putting a fix in place for **Automated Mailouts**. This will mark automated mailouts as complete when all recipients have a final status.
There are also other small bug fixes that will be included in this release update.
### Update Release 1.165.4 - April 23rd 2025
This update to release 1.165.0 will mainly impact the **Social** module as configuration changes will be made to ensure we are using the most up to date version of Facebook API.
There are also other small bug fixes that will be included in this release update.
---
# 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.165.0-19-march-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.