On Thu, 16 Jan 2003, Phil Chambers wrote:
> With Exim3 I used to be able to use a smartuser director such as:
>
> demo:
> driver = smartuser
> domains = xx:yy
> new_address = lsearch;/.../new_addresses
> transport = suitable_transport
>
> However, Exim4 has no correcponding router to do the same.
Indeed. I decided that redirecting and actually routing were separate
actions that should be kept separate instead of being mingled as in that
director.
> If I use an accept router I can't have a data option to generate a new
> address. If I use a redirect router I can't have a transport option.
> The only way I have worked out so far is to do:
> demo:
> driver = redirect
> domains = xx:yy
> data = lsearch;/.../new_addresses
> address_data = redirected_by_demo
> redirect_router = demo_2:
>
> demo_2:
> driver = accept
> condition = ${if eq {$address_data}{redirected_by_demo}{yes}{no}}
> transport = suitable_transport
Indeed again. That is similar to what the convert4r4 script produces.
> This seems so over the top for what used to be simple. Is there any chance of
> having a transport option added to the redirect router?
No, because (in general) it is a confusing concept to be simultaneously
redirecting an address (possibly to several other addresses) and routing
it (them) to a transport. I also wanted to get away from the concept of
routers that had optional "transport" settings (which is of course
saying the same thing). [Having said that, I agree that there is still
confusion in the area of routing to a pipe or file, where a transport
does get involved. So, I'm not consistent, am I? Is anybody? :-]
Philip
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
