 |
If we support authentication over IMAP, we couldn't show the user's full name (since we wouldn't have a way to get it) nor email addresses other than the system one (uid@SOGoMailDomain). |
 |
Sorry, I should have been clearer. We can provide names, e-mail-addresses, and other user data via an SQL database or LDAP, but we cannot use either for authentication. Put simply, we'd just need password checking to be done via IMAP. Apparently, this also is also true for the three users who discussed this feature request on the mailing list. |
|
|
I created a new feature request yesterday before finding this one, that would cover this use case and then some... "Support for separate/multiple AUTH and USER Db's, like dovecot" |
|
|
Maybe hybrid solution with SQL user datasource and type = imap, could address problem of unknown user's details (e.g. full name). Basically, we could have one (table or view) which keeps only user info (same as sql user source), and we could have IMAP server info which can be used for authentication. IMAP server should be configurable per user and per user source. IMAPHostFieldName user source (or user info) could be used to authenticate. |
|
|
+1 for this feature, makes perfect sense. |
|
|
Any update here? |
- Anonymous
