Re: [Kolab-devel] Kolab 3.x Extension to handle secondary domains internally (Multi-domain patched)

>  I would like to add the main domain dn to cn=kolab,cn=config for each
>  domain and thus be able to extract that to use as the search_base
> inside
>  postfix. That would help to have different users/lists/shared folders
>  using secondary mail-addresses to receive e-mail without mapping each
>  secondary domain to the main domain.
> 
>  I know this isn't possible as postfix looks today but that would be a
>  nice extension for all of us using multi-domain setups. In the case
> of
>  Kolab that would make it possible to handle all main as well as
>  secondary domains inside the kolab-webadmin and be a lot more
> flexible.

I am not really understanding what exactly you are trying to achieve, 
but I don't map my secondary domains to my primary domain, except maybe 
for mailman. I believe postfix already support most of what you want to 
do and that it's only a matter of easier and more flexible 
configuration. Please correct me if I am wrong.

I am running a server for different student organisations in my spare 
time. Each organisation has their own domain. Some are in the form 
my.domain.name and some in the form another.domain. I am describing what 
I did below because it might help figuring out a solution:

In my /etc/postfix/ldap/forward.cf file I have:
search_base = dc=%2,dc=%1

In my /etc/postfix/ldap/forward-subdomain.cf I have:
search_base = dc=%3,dc=%2,dc=%1

What I would like to do if anyone patch postfix is something like this 
because it would save me the work of duplicating my config files:
search_base = %dc .

I also have mailman mailinglist on both domains. I was struggling to 
implement it because I wasn't able to use pipe to command for all 
domains at once. I settled for using a postfix transport and 
postfix2mailman script as a quick and easy solution and haven't really 
done anything more about it. Messing too much with postfix configuration 
in production is not something I want to do and haven't been motivated 
for doing it on a test server.

My solution was to make up a new domain that does not exist in MX and 
forward mailman email to that from the postfix server. Because postfix 
is configured to accept mail to both domains that works well. I am going 
to add 19 mailman lists to a secondary domain soon and this regexp will 
come handy for that. I will include it in my main.cf soon:

/etc/mailman/virtual-regexp: 
/^(.+)-(post|admin|request|owner|join|leave|confirm)@(another.domain|third.domain) 
$/ [email protected]

/etc/postfix/transport: mailman.fribyte.uib.no mailman:

/etc/postfix/master.cf:
mailman             unix        -       n       n       -       -      
pipe
     flags=FR user=mailman:mailman  
argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}

Ketil