As I understand the ZEG:
(1) SOGo authenticates against the users defined in the LDAP server.
You can clone the 'sogo' user via Webmin and create additional LDAP users.
You then create Cyrus mailboxes, and in the ZEG, LDAP users can access
their mailbox.
Once you create the "new" mail domain (via GNUstepDefaults), you can
associate each user with it.
(2) SOGo is designed to replace Exchange Server.
THAT's why it authenticates against an LDAP Server (in my opinion) (or
as it works for me)
You can choose authentication against PAM or MySQL or an existing Active
Directory, but you've moved beyond the ZEG, and as I understand the ZEG,
it's meant to be a complete solution when configured.
The only issue is creating the "new" LDAP domain and identifying it in SOGo
(3) The inclusion of Samba4 in the ZEG is designed to replace Active
Directory.
You can use it or not. IF you use the Samba Server, you can join your
clients to a domain. The only gotcha I see is how you authenticate the
Samba users with LDAP or PAM (or with Samba itself)
We run the ZEG as an Exchange Server replacement. It provides mailboxes
and calendar services. How the mail domain was created is still a bit
fuzzy to me, but I believe it involves LDAP mostly.
All the rest of it comes together in the ZEG
On 03/02/2013 11:41 AM, Dave wrote:
Presumably, with Samba4, I could authenticate within Samba itself.
So, I think you have a choice.
Indeed, I see on the appliance Samba is on the ldap port and ldap is
on 3389, but since this is an *appliance* why install something no one
is going to use (what would be added to the LDAP on 3389?) and if it
is to integrate with an existing ldap server then that isn't in the
appliance. I'm still confused.
--
[email protected]
https://inverse.ca/sogo/lists
