Re: [exim] multi domain configuration ...

problem solved in the following way:

system_aliases_domain:
debug_print = "R: system_aliases for $local_part@$domain"
driver = redirect
domains = +local_domains
allow_fail
allow_defer
data = ${lookup{$local_part}lsearch{/etc/aliases.$domain}}

system_aliases:
debug_print = "R: system_aliases for $local_part@$domain"
driver = redirect
domains = +local_domains
allow_fail
allow_defer
data = ${lookup{$local_part}lsearch{/etc/aliases}}

and the aliases.v1.vserver.com is empty! now it works. maybe not the best
solution, but it works and is simply to administrate.. now there is 1 alias
file for each domain.

thank all for help (exim4 -d-all+route -bv ...)
regards, ji



-----Ursprüngliche Nachricht-----
Von: exim-users-bounces@??? [mailto:exim-users-bounces@exim.org] Im
Auftrag von Heiko Schlittermann
Gesendet: Donnerstag, 27. April 2006 09:21
An: exim-users@???
Betreff: Re: [exim] multi domain configuration ...

Heiko Schlittermann <hs@???> (Mi 26 Apr 2006 22:57:08 CEST):
> > mydomain1.com -> v1.vserver.com -> alias file doesn't exist
> > "/etc/aliases.v1.vserver.com" .. this is correct, no file, but ??

According to some other mail here: If I should read this as:
    the file /etc/aliases.v1.vserver.com does not exist

then of course you can skip the following test
    > What does exim4 -d-all+route -bv user1@??? tell you (and
us)?
and continue with creating the above mentioned alias file.

    # /etc/aliases.v1.vserver.com
    user1:  localuser1
    user2:  hans@???
    postmaster: your-local-postmaster-address
    *:  User does not exist.

I recommend using the '*' entry and changing the lsearch into lsearch*,
it least for me it avoids confusion, if the user is not found in the
"virtual" alias file but exists in you "global" /etc/aliases or is some
local user in your system.

Heiko