Dmitry Sergienko wrote: >>> I'm running Exim 4.12. One day I noticed that exim routes messages to MX
>>> with higher value than it is set for this machine. For example:
>>>
>>> I have domain example.net:
>>> example.net mail is handled (pri=10) by relay1.example.net
>>> example.net mail is handled (pri=25) by relay2.example.net
>>> example.net mail is handled (pri=150) by relay3.example.net
>>>
>>> relay2.example.net is machine where all happens.
>>> If relay1.example.net is in retry database, exim routes all messages to
>>> relay3.example.net, but it shouldn't do this, because relay2.example.net
>>> have higher priority (lower MX value) than relay3.example.net.
>>
>>
>>
>> Please post more evidence of an actual case of this, such as the output
>> of a delivery run with debugging (-d) turned on. Are you sure that
>> relay2 is not in the retry database? Are you sure that relay2 has an MX
>> record that points to an accessible host?
>
>
> Sorry for such long delay, just missed your letter.
>
> relay2 is machine where delivery is being done, so I don't understand
> how it can be in retry database or inaccessible host. Maybe you meant
> relay1? If so, it is in retry database, because it is inaccessible.
> But the main problem is that I don't want exim to try any other MX'es in
> this case. Otherwise I have a ping-pong beetween relay2 and relay3.
I've found a solution / my mistake.
I must not put @[] into ignore_target_hosts in router and manually
define hosts_treat_as_local.
