Have you checked out our open-source end-user interface on GitHub? It can be used either as it is, modified to fit your needs, or only as an inspiration for your own code. Since last time, we have updated it with a bunch of goodies, have a look and feel free to give us some feedback if you decide to try it.

Archiving feature

Your Halon nodes archives can now be managed directly from the Messages tab in the end-user interface. This feature allows you to browse, restore, resend and download messages from your archives, which can be very helpful if you have issues with your mail storage servers.

Archive

 A page to monitor rate-limits in real-time

This feature makes it possible to monitor rates from your Halon scripts. This could be useful if you monitor which customers or users that are sending large amounts of email or spam, which could be caused from compromised accounts, or to discover other anomalies. It can also be used to monitor if users or customers is close to rate limits.

Rate-limits

 Support for partitions for the database-log

Improves scalability and performance when using database logging.

 Support for database-log based graphs (In addition to the SOAP stats)

Makes it possible to create graphs directly from the end-users database-log in addition to using SOAP against the Halon servers.database-stats

Full support for using a PostgreSQL database

Added multiple themes to choose from

The enduser is based on twitter bootstrap which makes it very easy to change between different bootstrap themes. We’ve provided different themes to choose from in the settings file but you could easily implement your own themes as well.

 The ability to black-/whitelist senders directly from the preview page

 A datastore page to store various kinds of data that can be fetched by the Halon node(s)

The datastore is very useful to store various kind of data that can be fetched by the Halon nodes. An example could be overrides of rate limits for different customers, data for routing and destination servers, specific domain or user settings, SASL authentication data or data for DKIM signing.

Data store

A page to create and manage database users and their permissions

Improved database user management. Create and manage users, edit permissions and passwords.

User management