Hi Dominik,
thank you for your answer. The script ldap_check_rcpt return
"false" when something is wrong with the ldap response or if the user
isn't an internal user.
So the condition is false and the lookup router would be taken, or not?
What I don't understand is why exim send the mail back to the sender
after one minute if he could not access the "new" destination IP 217.196.145.212.
Normaly exim tries it to 4 days but in this special case it only
tries it for one minute :-(
To use your ldap_down router could be a way to deal with that problem
but if I find a way not to implement an aditional ldap lookup it
would be my first choice because there is a heavy load on the
gateways.
Regards,
Hans
-------- Original-Nachricht --------
> Datum: Tue, 22 Jul 2008 17:53:45 +0200
> Von: "Schramm, Dominik" <dominik.schramm@???>
> An: exim-users@???
> Betreff: Re: [exim] Router problem
> Hi Hans,
>
> Hans Klose wrote on Tuesday, July 22, 2008 12:55 PM:
>
> > The first router the mail passes is a query I wrote in perl.
> > He looks if the User is in our AD and in a MYSQL DB and if
> > so it will be forwarded to our internal Mailserver.
>
> We have the same setup here, however, I extract all the valid
> AD addresses into a database (sqlite) twice a day and check
> against this database in my routers. That way the availability
> of the LDAP servers is irrelevant for the mail server.
>
> > I thought if exim can not reach 217.196.145.212 it will try
> > it again later and later and so on
> > and send the mail back after 4 Days. Or if the LDAP server is
> > reachable again exim
> > send the mail to the internal server, as he should.
>
> What does the sub/script ldap_check_rcpt return when the LDAP
> server is down? If it's the same as when the LDAP server is
> reachable, then exim should use the ordinary retry mechanism.
> If it's not the same, then exim cannot know that the router
> ldap_down should nevertheless be used (and the message deferred)
> and control should not pass on to the next router. In the latter
> case the condition would have to be extended to cover LDAP
> outages.
>
> Example: You could check the availability of the LDAP server in
> a redirect router before the actual router. Something like this
> (this is not guaranteed to be syntactically valid):
>
> ldap_down:
> debug_print = "R: LDAP server is down"
> driver = redirect
> data = :defer:
> condition = ${if and { {eq{${perl{ldap_check_ldap_reachable}}}{LDAP
> is unreachable}} \
> {eq{${perl{ldap_check_rcpt}{router}}}{true}}
> }}
>
> ldap_lookup:
> debug_print = "R: LDAP Lookup Router"
> driver = manualroute
> condition = ${if eq{${perl{ldap_check_rcpt}{router}}}{true}{yes}{no}}
> self = ${if eq{${perl{ldap_check_ldap_reachable}}}{LDAP is
> unreachable} {defer}{pass}}
> route_list = * 192.168.0.10
> transport = remote_smtp
>
> Regards,
> Dominik
>
>
>
> --
> ## List details at http://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
--
GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion!
http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196
