Hi,
Thanx for the response. Unfortunately, this is also not the case. The error
is typical defer - it is just a "connection refused" to the HOST_MASTER. Or
"connection timeout". In that situations there should be a try to send the
message to HOST_FALLBACK. But it not happens. At all, no matter of the IP,
domain name, other options and so on. In my case exim behaves like ignoring
the option.
I looked into the source code, but didn't find the answer. It seems there is
some unobvious dependency between fallback_hosts and some other option(s).
It is not described in the specification, so probably this is some very
spicy bug.
Maybe you can send to priv some example of working configuration that uses
the fallback_hosts option?
MJS
On 2017-09-07 15:06, Jeremy Harris wrote:
> On 06/09/17 17:52, Marcin Sacha wrote:
> > If the connection to HOST_MASTER is refused
>
> The fallback_hosts option does not operate for a permanent rejection.
>
> > or timeouted, the message is
> > retried without calling HOST_FALLBACK. It is also not called after cut
off
> > time (after last retry).
>
> Those I can't account for, unless the permanent rejection for the host
> was still in your hints database - in which case Exim assumes that
> it would get the same response, and not even try. To test that,
> remove the database file (or edit it with the exim_fixdb); see
>
>
<
http://exim.org/exim-html-current/doc/html/spec_html/ch-exim_utilities.html
#SECThindatmai>
http://exim.org/exim-html-current/doc/html/spec_html/ch-exim_utilities.html#
SECThindatmai
>
> --
> Cheers,
> Jeremy
>
>
