May's release brings important updates aimed at improving performance, accessibility, and user autonomy. This month, the spotlight is on a frequently requested improvement to the database management process—users with the correct permissions can now add and move database fields directly in the updated interface. This enhancement simplifies field management and reduces dependency on support.
Below you will find a highlighted feature and the full release notes:
Add and move database fields
Managing your database is now easier and more accessible. The option to add new database fields has been moved to the updated user interface. Additionally, users with the appropriate permissions can now add new fields themselves—eliminating the need for support requests.
This update is part of the broader effort to unify older and newer features and provide more control to users.
Users who can add database fields:
- Admin
- Owner
- Corporate
- Franchise
If you want to learn more about how to add and edit database fields, read the article: Database fields.
Full release notes
Improvements
Accessibility issues forms
Based on WCAG guidelines and client feedback, several improvements were made to form accessibility:
- Checkboxes and radio buttons are now properly grouped
- Alerts are correctly linked to the appropriate input fields
- The general alert code was updated so users are properly notified when an alert appears
Central customer domain service
The handling of custom domain certificates has been migrated from Certbot to Caddy. Certbot was outdated and required significant maintenance by the TechOps team.
To support this change, a central service was developed to validate customer domains. This allows Caddy to automatically issue HTTPS certificates.
Image scaling performance improvement
Image scaling now takes place on the frontend instead of the backend. This significantly improves the performance of the Mail+ software.
Bug fixes
-
Extra spaces added when saving message
In V1 messages, saving repeatedly added extra spaces between MSO code. Over time, this increased the message file size and could eventually prevent it from being saved. -
Error when saving messages with multiple URLs on one line
Messages with several URLs on a single line sometimes triggered a red error message and could not be saved. -
Expiring credits could lead to a negative balance
Previously, if an account had 0 credits and sent messages via Automation, the credit balance could drop below zero—this was expected. However, after new credits were purchased and later expired (without new emails being sent), the balance could drop below zero again.Example- Balance: -20 credits
- User buys 40 credits → New balance: 20 credits
- One year later, 40 credits expire → New balance: -20 credits
Expected result: After credit expiration, the balance should be 0 credits, not negative.
-
Mailing stuck in STOPPING status
If a mailing was cancelled before the first batch started, it stayed stuck in STOPPING status. After 24 hours, it changed to ERROR. Now, such mailings are fully cancelled and removed from the list. -
No retry on SendAPI calls
Some ActivateMailing calls failed silently due to lack of retry logic. As a result, mailings remained stuck in ACTIVE status. This issue has now been addressed. -
Status set to QUEUED after two resends
If an account already had the maximum number of active mailings, resending a mailing set the status to QUEUED instead of sending it directly. This behavior has been corrected.