On 20.03.2018 20:03, Graeme Fowler via Exim-users wrote:
> On 20 Mar 2018, at 12:03, Konstantin Boyandin via Exim-users
wrote:
>> However, the cases I mention do not print anything like above to
>> main.log (and MX records are normally resolved at that moment, both
>>
On 20 Mar 2018, at 12:03, Konstantin Boyandin via Exim-users
wrote:
> 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').
Just a
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
: all relevant MX records point to non-existent hosts
However, the cases I mention do not print anything like above to
On 19 Mar 2018, at 14:39, Konstantin Boyandin via Exim-users
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
Hello,
Having a grave problem with recently compiled Exim 4.90.1 (running on
Ubuntu 16.04 64bit).
Primary domain: example.com
In /etc/aliases:
user: us...@example.net,us...@example.net
When I run command like
exim -bt u...@example.com
Exim prints correct MX records for every particular