Hmmm, with exim4 I think it would just work as is... as long as those 2
routers come before the one for local delivery (virtual_local_delivery).
But in exim3 I'm not sure how you would do that. I believe exim3 uses
"local_domains = " to determine whether to use a router or a director. So
how would you reroute to a different host once you're in a director? Maybe
you could hack something up with the system filter, but I'm not sure how.
Is upgrading to 4.04 an option? :-)
----- Original Message -----
From: "Joel Vandal" <jvandal@???>
To: "Rick Ennis" <ennis@???>; <exim-users@???>
Sent: Wednesday, April 24, 2002 10:54 AM
Subject: Re: [Exim] EXIM -> WEBSHIELD -> EXIM -> INTERNET
> Hi,
>
> Thanks, this work and my mail are now routed to our WebShield e500 but
this
> solution work if the "recipient" isn't a local user.
>
> If the recipient domain is on our localdomain list then the mail is sent
> directly to the user mailbox using "virtual_local_delivery"
>
> Does exist a way to "force" all mail to route using "IN_to_webshield"
both
> if the recipient is a local or remote domain ?
>
> Thanks,
>
> Joel
>
> === Original Message ===
> > I think I've done something kind of similar with WebShield. It was
easy
> > enough. Basically setup two routers on smtp2. First, one that sends
> > anything that *didn't* come from the smtp1, *to* smtp1:
> >
> > # change 99.99.99.99 to the IP of your webshield smtp1 machine
> >
> > IN_to_websheild:
> > driver = manualroute
> > condition = "${if or {{eq{$sender_host_address}{99.99.99.99}}
> > {eq{$received_protocol}{local}}} {no}{yes}}"
> > transport = remote_smtp
> > route_list = * smtp1.yourdomain.com
> > ignore_target_hosts = 127.0.0.0/8
> >
> > # And second, your existing router that [presumably] does a DNS lookup
and
> > sends the message back out:
> >
> > OUT_via_dns:
> > driver = dnslookup
> > transport = remote_smtp
> > # domains = +relay_domains # are you restricting to
> > certain domains?
> > ignore_target_hosts = 127.0.0.0/8
>
>
>
>
>
