<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
In <a class="moz-txt-link-freetext"
href="http://docs.kolab.org/howtos/multi-domain.html">http://docs.kolab.org/howtos/multi-domain.html</a>,
section "Alias Domain Name Spaces for Hosted Kolab Domains", it si
shown that files
/etc/postfix/ldap/example.org/local_recipient_maps.cf and
/etc/postfix/ldap/example.org/virtual_alias_maps.cf contains<br>
search_base = cn=kolab,cn=config<br>
<br>
Is this correct? Shouldn't it be <br>
search_base = dc=example, dc=org<br>
<br>
Also shouldn't<br>
* the files virtual_alias_maps_mailforwarding.cf and
virtual_alias_maps_sharedfolders.cf be adapted too?<br>
* the postfix configuration adapted accordingly
(local_recipient_maps, virtual_alias_maps and
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
transport_maps)?<br>
<br>
Shouldn't we also choose between the approach with search_base =
dc=%2,dc=%1 described in section postfix changes (and then not
support alias domain space) or have the approach with the explicit
search base - or have a mix of both if some domains do have aliases
or don't? It was not clear for me.<br>
<br>
Also note that in my fresh install of Kolab 3.2 on CentOS 6.5, there
is no
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
alias_maps_catchall.cf file, which cause trouble as it is always
added to the virtual_alias_maps of postfix. SO either there was a
glitch in the setup that did not create the catchall, or there is a
glitch in the howto.<br>
<br>
If you confirm I am right, I would be happy to update the page
accordingly.<br>
<br>
Best regards<br>
<br>
Thierry De Leeuw<br>
<br>
</body>
</html>