Hello Graeme, When there were (quite rare) actual connectivity issues, I saw the messages like
2018-03-19 12:58:22 1exnoM-0004qJ-Bn ** us...@example.net <u...@example.com>: all relevant MX records point to non-existent hosts However, the cases I mention do not print anything like above to main.log (and MX records are normally resolved at that moment, both manually and via output of 'exim -bt u...@example.com'). I'll do the debug run at first opportunity. I consider trying manualroute for this particular domain, since staying on vulnerable Exim version isn't fun, either. Regards, Konstantin On 19.03.2018 22:03, Graeme Fowler via Exim-users wrote: > On 19 Mar 2018, at 14:39, Konstantin Boyandin via Exim-users <exim-users@exim.org> wrote: >> I would appreciate pieces of advice on how to handle this. Thank you. > > It would appear that you can reproduce the problem, so running in debug mode would be an immense help, then posting the output. > > In the example you gave first, did the message try the MX servers and fail through a deferral (or connection failure) to use the A record? > > Regards > > Graeme > -- ## List details at https://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/
