Looks like I figured out part of the issue. The destination server is
refusing to accept mail from some of our Exim servers. They have their
Exchange connector locked down so we get this on some connections:
*421 4.3.2 Service not available, closing transmission channel*
So at some point Exim records in its internal systems that it is not
possible to deliver to that server and will stop trying totally?
Rob
On Thu, May 14, 2015 at 8:48 PM, Rob Gunther <redrob@???> wrote:
> I have exim setup to hold mail for as long as 7 days in the event of a
> delivery problem to the remote server.
>
> My retry section is quite simple.
>
> * * F,2d,15m; F,7d,1h;
>
> This normally works just fine. However sometimes I see a message rejected
> right away, it never tries delivery at all.
>
> In this log a message is received an rejected in the same second, without
> even tryin the delivery at all.
>
> 2015-05-13 18:32:00 1YsbRo-0003OZ-JD <= mj@??? H=(s81a.ikbb.com)
> [192.168.81.5] P=esmtps X=TLSv1:DHE-RSA-AES256-SHA:256 S=127222 id=
> 676D93E5D90427499D1C4B805FE4FA4F0D7BAE@??? T="RE:
> TEST" from <mj@???> for ds@???
>
> 2015-05-13 18:32:00 1YsbRo-0003OZ-JD ** ds@??? F=<mj@???>
> R=ikbb_router T=remote_smtp: retry time not reached for any host after a
> long failure period
>
> 2015-05-13 18:32:00 1YsbRo-0003Rt-Kv <= <> R=1YsbRo-0003OZ-JD U=mail
> P=local S=110175 T="Mail delivery failed" from <> for SRS0=PTyV=FY=
> rocore.com=mjames@???
>
> 2015-05-13 18:32:00 1YsbRo-0003OZ-JD Completed
>
>
> What can cause this type of thing? Why is Exim not holding the message
> for delivery.
>
>
> Rob
>
>
>
