Changes

*LDAP/AD (not implemented in this howto)

*LDAP/AD (not implemented in this howto)

Using the '''db-plugin''' in the zarafa-configuration, let you make your zarafa-users in the MySQL-zarafadatabase, with a separate user-password for every zarafa-user. So, you make your Zarafa-users 'by hand' in the zarafa-MySQL-database.  You can enable maildelivery for a SME/unix-user to a zarafa-user with the same logon-name.<br>

Using the '''db-plugin''' in the zarafa-configuration, let you make your zarafa-users in the MySQL-zarafadatabase, with a separate user-password for every zarafa-user and a store. So, you make your separated Zarafa-users and the stores for these zarafa-users one by one in the zarafa-MySQL-database.  There is no syncronisation between the SME-user-passwords and the Zarafa-user-passwords. You can only enable maildelivery for a SME/unix-user to a zarafa-user with the same logon-name.<br>

When using the '''unix-plugin''' in the zarafa-configuration, zarafa makes a store for every SME/unix-user on your system, except for those who are excluded by the template used in this howto.<br>

When using the '''unix-plugin''' in the zarafa-configuration, zarafa makes a store for every SME/unix-user on your system, except for those who are excluded by the template used in this howto. Zarafa uses the passwords of the SME/unix-users. You can enable maildelivery for a SME/unix-user to Zarafa.  The unix-plugin seems to be your best choice if all your SME-users will use Zarafa Webaccess/Microsoft Outlook, and you don't need a multicompany-environment.<br>

In a multicompany-evironment every company has his own Global Adressbook and public folders.

In a multicompany-evironment every company has his own Global Adressbook and public folders.