Multi-domain setup with Kolab 3.3 on CentOS 7

[Gelpi Andrea]

Il 01/10/2014 20:11, Cornelius Hald ha scritto:
> Here are the changes I did based on the default install:
> 
> [root a kolab etc]# git diff b4320c010acede8287717ae60da671cb565dc0d5
> imapd.conf
> diff --git a/imapd.conf b/imapd.conf
> index baa330b..b612131 100644
> --- a/imapd.conf
> +++ b/imapd.conf
> @@ -49,3 +49,11 @@ delete_mode: delayed
>  expunge_mode: delayed
>  flushseenstate: 1
>  postuser: shared
> +
> +# Added for multi-domain support
> +ldap_domain_base_dn: ""
> +ldap_domain_filter:
> (&(objectclass=domainrelatedobject)(associateddomain=%s))
> +ldap_domain_name_attribute: associatedDomain
> +ldap_domain_scope: sub
> +ldap_domain_result_attribute: inetdomainbasedn
> 

I posted some months ago in this list the solution I found.

In /etc/imapd.conf I had to change:

ldap_base: dc=%2,dc=%1
ldap_group_base: dc=%2,dc=%1
ldap_member_base: ou=People,dc=%2,dc=%1

Now I can have distinct domain, but with only two levels.


Similar chenges must be done in other components.

Documentation in docs.kolab.org is not complete.

It was kolab 3.2 on debian 7.5.




-- 
ing. Andrea Gelpi
***************************************************
La Terra non la abbiamo ereditata dai nostri avi,
ma la abbiamo presa in prestito dai nostri bambini.
***************************************************
We do not inherit the Earth from our parents,
but borrow it from our children.
***************************************************