Hello!
> I'd hazard a guess that this is where your problem lies - this isn't
> really a "failure" that you could call by a name, just... silence. Now
> that *should* result in trying the second MX.
>
> What do you see if you grab one of the message-IDs you have queued and
> do:
>
> exim -d -M MESSAGEID
>
Impossible to do as I manually rerouted this message to the second MX. I
tried to send new message today and wondering - MX fallback is working
now! But I have restarted exim before. Ok, the problem is solved and now
I know what diagnostic is needed if the problem returns.
> ?
>
> Graeme
>
>
>
--
With respect,
Boris
