Well Magnus, i wish i can test all by myself, but it is a working server,
and my users will kill me, if i startt testing. I just tried to make union
queries in mysql and it didnt work, i guess some syntax errors ..How do a
join 2 lookups with exim not with mysql, i tried as from an example,
joining by "/"
data = ${lookup mysql{SELECT sendto FROM aliases \
WHERE (username='$local_part' AND domainname='$domain') \
OR (username='*' AND domainname='$domain')}}/
${lookup mysql{ SELECT id FROM users \
WHERE id='${quote_mysql:${local_part}@${domain}}' }}
but it gives an error( option setting expected). Searched in exim manual
dindn't find a single hint.
Thank you!
Oleg R.
---------------------------- Original Message ----------------------------
Subject: Re: [exim] Unrouteable address ERROR
From: "Magnus Holmgren" <holmgren@???>
Date: Thu, May 4, 2006 3:16 pm
To: exim-users@???
--------------------------------------------------------------------------
Thursday 04 May 2006 13:25 skrev oleg@???:
> To make message to pass through virtual_user down to aliases, i have put
UNSEEN word..everything is good, messages are working and aliases too,
but an error message is generated with "Unrouteable address ERROR" back
to the sender. How can i accomplish that and not get that messages???
"unseen" is not a good idea here. It generates a copy while the original
will continue down the routers as if Exim didn't see the first router,
hence "unseen". If none of the remaining routers can handle the address, a
bounce message will be generated.
But you should be fine even without "unseen". If the data lookup returns
nothing, the router declines and the next router gets the chance. If you
want some addresses to be routed to a maildir *as well* as some other
address, then you'd better either a) merge the two routers (use an SQL
UNION statement or simply two separate lookups joined together), b) let
mysql_aliases return the original address together with the aliased
address(es) (and put mysql_aliases back on top) when the original address
is a virtual user (but that would be almost the same as merging the
routers), c) add a third router that somehow handles the special case or
d) make sure that the aliases table aliases such addresses to themselves
as well.
--
Magnus Holmgren
holmgren@???
