Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 6 ] [+]
Feature request to allow adding email aliases cross-domain (if under management of the same administrator). This would allow for situations where there are multiple domains, with some shared and some unique mailboxes on either domain.
Currently LDAP authentication is only possible by providing the valid LDAP username/password. This was implemented by design, to avoid the requirement for elevated LDAP permissions. However if the LDAP mailbox sync is used, such elevated permissions are already granted. Therefore it would be useful if you can sync e.g. the sAMAccountName to be used as LDAP authentication username for a specific email address, so the ...more »
Feature request to make it possible to rewrite all URLs in an email to a third-party or buildin Sandbox environment to scan the website when the user attempt to visit it.
It may be nice to allow parent accounts to set a custom identifier/text for each of their sub-admins, which cannot be changed by the sub-admin and is available in reporting available to the parent account.
As the Mail Assure delivery IP addresses frequently change, it can be hard to manage a large number of firewall/O365 deployments to restrict email from the Mail Assure IP space. The header-based alternative described in the KB (https://kb.spamexperts.com/36683-delivery-restriction-examples/286647-office-365) can be spoofed, and hence is not 100% secure. A better alternative should be provided which cannot be spoofed and ...more »
Add a feature to have the platform generate a recipient email address accepting journal messages for the email archiving service. This would eliminate the need to setup your own hostname with valid MX records to allow for journal-based email archiving.