On Mon, 8 Nov 1999, Mohammed Qadeer wrote:
>
>
Oh! What a pain. You have put all the "meat" of your message into an
attachement which Pine isn't showing in the reply message. I will have
to fish it out separately in order to quote it ....
> e.g pancho@??? is aliased as p12345@??? however
> $local_part contains pancho.
>
> My Director is below
>
> virtual_alias:
> driver=aliasfile
> qualify_preserve_domain
> search_type=mysql
> query="select emailid from EMAILADDS where domain='${domain}' and
> alias='${local_part}'"
> transport = virtual_local_delivery
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is the problem. You should *not* set a transport on an aliasfile
director that is just doing aliasing operations. You should just let it
generate the new addresses, and then each of them will be reprocessed
independently (by directors or routers as required).
If you do set a transport, you are just using the aliasfile mechanism to
recognize a list of local parts. The data that gets looked up is
ignored, even if it is just a single address. (Of course in general it
can be many addresses.)
> This part is fine, the transport ...
> virtual_local_delivery:
> driver=appendfile
> file= /mail/$local_part
> #file=/mail/${lookup mysql{select emailid from EMAILADDS where
> domain='${domain}' and alias='${local_part}'}{$value}}
> delivery_date_add
> envelope_to_add
> return_path_add
> group =exim
> user = exim
> mode=0644
>
> Now I can get it to deliver to /mail/p12345 if I uncomment the second
> line, but this seems like a waste of a query. Which variable contains
> the "new" local_part, I have even tried $local_part_data, but this also
> fails (in fact it is empty).
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Government Policy: If it ain't broke, fix it till it is.
