Re: [Kolab-devel] Kolab 3.x Extension to handle secondary domains internally (Multi-domain patched)
"Jeroen van Meeuwen (Kolab Systems)" <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Message-ID | <[email protected]> |
On 2014-04-02 20:35, Rickard Osser wrote: > 2014-04-02 17:48 skrev Ketil Kvifte: >>> Yes, if you run kolab in single domain it does but not in >>> multi-domain as >> it's implemented with separate dn's (dc=x,dc=y) >> >>> for each organisation. >> >> There is a difference between adding 2 domains, and adding 1 domain >> with 2 >> aliases. domain1.com is separate and domain3.com is an alias for >> domain2.com >> >> # domain1.com, kolab, config >> dn: associateddomain=domain1.com,cn=kolab,cn=config >> associatedDomain: domain1.com >> objectClass: top >> objectClass: domainrelatedobject >> objectClass: inetdomain >> >> # domain2.com, kolab, config >> dn: associateddomain=domain2.com,cn=kolab,cn=config >> associatedDomain: domain2.com >> associatedDomain: domain3.com >> objectClass: top >> objectClass: domainrelatedobject >> objectClass: inetdomain >> >> Making an example user on domain2.com I get: >> >> postmap -q [email protected] >> ldap:/etc/postfix/ldap/local_recipient_maps.cf >> [email protected] >> >> postmap -q [email protected] >> ldap:/etc/postfix/ldap/local_recipient_maps.cf >> >> No output here. I guess that's what you want fixed somehow. > > You nailed it, that is exactly what I want to do! :) > Does this help? http://docs.kolab.org/howtos/multi-domain.html#alias-domain-name-spaces-for-hosted-kolab-domains Kind regards, Jeroen van Meeuwen -- Systems Architect, Kolab Systems AG e: vanmeeuwen at kolabsys.com m: +44 74 2516 3817 w: http://www.kolabsys.com pgp: 9342 BF08