What’s new this week:
LDAP Mailbox Sync now allows to map an LDAP username
The LDAP authentication feature allows mailboxes to authenticate to the control panel using their associated LDAP username/password. On some environments the users are not aware of their actual LDAP username, and expect to authenticate using their email address. We have now added a mapping option to the “LDAP mailbox sync”, which allows the user to look up and store the LDAP username as attributed to the email address. When this mapping is set, the system will allow LDAP authentication using the email address instead of the LDAP username.
BCC to sender option added when composing a reply
When composing a reply from the web interface, it is now possible to deliver a copy of the email to the sender. This ensures the sender having a local copy when using this feature.
- Resolved: fixed an issue where excessive memory could be used by the LDAP Mailbox sync (#442)
- Resolved: fixed a delay that could occur when migrating log entries between filtering and logging servers that are distant from each other (#451)
Front-end / GUI:
- Resolved: fixed an issue where the archive usage export could show “None” rather than 0 (#637)
- Improved: sending new messages and replies now optionally send a blind-copy (BCC) to the sender (#464, #197)
- Improved: the preview API logs are now searchable by admin and domain, not internal admin and domain IDs (#623)
- Added: the LDAP sync system has a new ‘username’ mapping type (#589)