Topic: New feature in upcoming iRedAdmin-Pro: self-service.
Just want to share this new feature which will be available in upcoming iRedAdmin-Pro release: self-service. We hope this new feature will help free mail administrators (and, probably, HR).
With self-service, normal user can login to iRedAdmin-Pro to manage their own profile, including:
Name, preferred language in iRedAdmin-Pro.
Set mail forwarding
Manage (view, delete or release) quarantined Spam/Virus
Manage per-user white/blacklist
Manage per-user spam policy
Domain admin can restrict which profiles can be updated by user in domain profile page (under tab "Advanced"). If you don't want to let user forward his email, you can disable this preference in domain profile page.
Per-user white/blacklist in self-service is implemented by Amavisd and SQL integration.
Currently, no matter which backends you chose, iRedMail will create a SQL database "amavisd", 4 SQL tables (mailaddr, policy, users, wblist) are used to store per-user white/blacklists and per-user spam policy, Amavisd needs read-only privilege on them if you enable '@lookup_sql_dsn'.
Another 4 tables (maddr, msgs, msgrcpt, quarantine) are used to store basic info of in/out emails, and quarantined mails. Amavisd needs read-write privileges if you enable '@storage_sql_dsn' -- This is enabled by default in iRedMail.
With OpenLDAP backend, we have LDAP integration enabled in Amavisd by default. Amavisd can query per-user spam policies and white/blacklist stored in ldap user object. To reduce complexity of iRedMail architecture and simplify iRedAdmin-Pro, we will use SQL integration in Amavisd for all backends and drop LDAP integration for OpenLDAP backend in next release of iRedMail.
Screenshots of self-service in iRedAdmin-Pro:
*) Manage quarantined mails.
*) Manage per-user white/blacklists.
*) Manage per-user spam policy.