2005-08-01 11:58:07 +00:00
|
|
|
|
|
|
|
Some notes on managing Kolab accounts with LAM:
|
|
|
|
|
|
|
|
|
|
|
|
1. LDAP Suffix
|
|
|
|
|
|
|
|
You must create your accounts directly in the LDAP root (e.g. dc=company,dc=com).
|
|
|
|
If you use other suffixes like ou=people,dc=company,dc=com the Kolab daemon will
|
|
|
|
not recognize them (e.g. create no mailbox).
|
|
|
|
|
|
|
|
|
|
|
|
2. Deleting accounts
|
|
|
|
|
|
|
|
If you want to cleanly delete accounts use the "Mark for deletion" button on the
|
|
|
|
Kolab subpage of an account. This will also remove the user's mailbox.
|
|
|
|
If you delete the account from the account list (which is standard for LAM accounts)
|
|
|
|
then no cleanup actions are made.
|
|
|
|
|
|
|
|
|
|
|
|
3. Managing accounts with both LAM and Kolab Admin GUI
|
|
|
|
|
|
|
|
The Kolab GUI has some restrictions that LAM does not have.
|
|
|
|
Please pay attention to the following restrictions:
|
|
|
|
|
|
|
|
- Common name in LAM
|
|
|
|
The common name must have the format "<first name> <last name>".
|
|
|
|
You can leave the field empty in LAM and it will automatically
|
|
|
|
fill in the correct value.
|
|
|
|
|
|
|
|
- Changing first/last name in Kolab GUI
|
|
|
|
Do not change the first/last name of your users in the Kolab GUI!
|
|
|
|
The GUI will change the common name which leads to an LDAP object class
|
2005-08-04 17:58:54 +00:00
|
|
|
violation. This is caused by a bug in the Kolab GUI.
|
|
|
|
|
|
|
|
|
|
|
|
4. Installing LAM on the Kolab server
|
|
|
|
|
|
|
|
You can install LAM in the directory "/kolab/var/kolab/www" which is
|
|
|
|
the root directory for Apache.
|
|
|
|
The PHP installation already includes all required packages.
|
|
|
|
|
|
|
|
!!! Attention !!!
|
|
|
|
LAM will not work if installed on the first stable release (20.06.2005)
|
|
|
|
of Kolab 2. The provided PHP release has some bugs which make it
|
|
|
|
impossible for LAM to work properly.
|
|
|
|
Hopefully this will change with the next release of Kolab 2.
|