What’s new this week
Summary Information
When using a page that provides a table that includes one or more columns that is a number, you can now optionally include an average or total summary row. If you group the results, then you’ll get both average/total rows for each group, and an overall row.
Changelog
Filtering (services):
Changelog
Filtering (services):
Changelog
Filtering (services):
Changelog
Filtering (services):
What’s new this week:
LDAP distribution list flag sync
The LDAP mailbox synchronization system has a new attribute that may be copied from the LDAP server: indicating if the mailbox is a distribution list. A default mapping is provided for newly added domains, so, if your LDAP server is configured in a standard way, and you’re using the default mapping, your distribution lists should be picked up automatically.
What’s new this week:
Admin level custom filtering rules
It’s now possible to create filtering rules at admin level (that apply to all domains linked to that admin, including indirectly). To do this, simply use the “Admin Rules” tab and select the appropriate admin when creating the rule.
Admins also have a new “Inherited Rules” tab, where they can see (but not edit) rules that have been created by higher level admins. Domain-level users are able to see, but not edit, the rules that are applied to their mail (on the “Admin Rules” tab). If a domain-level user opts out of using the default rules, they are opted out of using the admin rules as well.
What’s new this week:
Addition of Admin Aliases for login
A new page has been added “Manage Admin Aliases”. This page is used to configure multiple user/password credentials to log in as the same admin. For example, if you have three users that manage the same set of domains, then you can create an admin alias for each of them, rather than sharing the same set of admin credentials.
When an admin alias is used to log in, the user has the same permissions as the primary admin. You can see in the top bar the name of the main admin, and actions taken by the user will be logged against the admin alias for auditing purposes.
What’s new this week
Option to require delivery using TLS
The normal behavior for mail delivery is that a secure (TLS) connection is established whenever both the sending and receiving servers support it; all our servers support TLS, so a TLS connection will be used as long as the server on the other side has support. If a secure connection is required (ie. if one cannot be established delivery should fail) then the best way to handle this is to use DANE. However, DANE cannot require a TLS connection only for specific mailboxes, and can be complicated to configure, as it requires DNSSEC. Continue reading
Filtering (services):
