The reason for I have asked to force external login with the email account instead of the user account, with SOGo (and maybe Roundcube but SOGo is my preference):
The goal: Email server for multiple (different) domains.
Notes:
The NS is used only as a email server (hosting for multiple email domains, no PDC or/and AD Integration).
Only the following services will be enabled for the user accounts: Mailbox and Password Expiration (no Shared Folders - Samba).
Because NS is not designed (yet) for this function (complete separate domains), all users (user accounts) are in the same place. In this case, we cannot create two (or more) users with the same account.
I give you an working example:
In a national project, I must set an email server (I prefer to do this with NS) for about 70 email domains. At least one email address will be contact@domain(1,2,3,…70).ro
I can only create users for each domain, like this:
user: contact.domain 1 with the email: contact@domain1.ro
user: contact.domain 2 with the email: contact@domain2.ro
.
.
.
user: contact.domain 70 with the email: contact@domain70.ro
It’s easy and better to login in SOGo with the email address than the user account.
I think I will create a new post in Feature section with this goal (NS as Email server for multiple (different) domains with SOGo), because there are others request for this:
I agree, Samba DC brings a major change to the LDAP tree and any service using it (SOGo included) must be fixed accordingly.
I was tempted to do it in ns6, because SOGo has some problems with the LDAP tree in ns6. However as ns7 is coming, I’m not sure anymore it is worth the effort.
Yes it is, but they changed the configuration syntax/file/db at least 2 times.
I don’t know if it worth it to switch again to the config file. GNUStep is hugly, but for now it works.
Few days ago @davidep said he wanted to switch to sogo.conf…who knows!
How to hide (disable) “mail users” (Global Address Book) on SOGo 2.3.8 (update to this version of SOGo from Software center beginning from today - Thank you @giacomo ! ):
The principle will be the same, some templates to /etc/sogo/sogo.conf however for a quick modification, you can tweak directly the sogo.conf files, of course only for testing purpose.