I would very much like the ability to be able to use separate AUTH and USER Databases, like dovecot can do now.

Use case:

We have Windows Server 2008R2 AD servers, but we (intentionally) do NOT use SSO.

Meaning, users email passwords are different from their Domain Login passwords and are stored in a separate SQL database. This allows us to assign much stronger passwords for email, but let them have less secure domain login passwords.

Since SOGo does not provide a way to create/manage SQL based user groups (for ACLs), we cannot use AD Groups when assigning ACLs, so I have to add each and every user to the main Shared Calendars and Address Books... this is a major pain.

We are looking into adding support for user groups in the SQL based user management software we use (postfixadmin), but it currently has none, and may not for some time (or ever).

If SOGo could define/use separate AUTH and USER DBs, like dovecot does, I could tell it to use AD for the USERDB stuff (getting group information, etc), but use dovecot for all AUTHing.

This would provide maximum flexibility for setups that do not store everything in LDAP (or AD).

Thanks for listening...