Hi Ian, Thanks very much for your reply. So, hypothetically, I could specify a retry rule like this to cause the auth_failed error to be retried for a long time:
* auth_failed G,16h,1h,1.5 Thanks, Ken On Thu, May 1, 2014 at 9:18 AM, Ian Eiloart <[email protected]> wrote: > > On 29 Apr 2014, at 18:11, Ken Simpson <[email protected]> wrote: > > > Is there a way to have Exim treat a 500-failure on SMTP authentication > with > > a smarthost as a transient error, and simply re-queue the message rather > > than generating an NDR? > > > > Our smart host sometimes generates a 500 on authentication, but it's not > > really a permanent error - just a temporary glitch. I don't want our > users > > to see NDRs in this case. > > The documentation for hosts_require_auth suggests that your desired > behaviour is the default behaviour for the listed hosts. List them here, > and you should be OK. But, check that your retry rules are giving > sufficient latitude, otherwise messages will bounce if the smart host > persistently refuses authentication. > > hosts_require_auth > > This option provides a list of servers for which authentication must > succeed before Exim will try to transfer a message. If authentication fails > for servers which are not in this list, Exim tries to send unauthenticated. > If authentication fails for one of these servers, delivery is deferred. > This temporary error is detectable in the retry rules, so it can be turned > into a hard failure if required. See also hosts_ try_auth, and chapter 33 > for details of authentication. > > -- > Ian Eiloart > Postmaster, University of Sussex > +44 (0) 1273 87-3148 > > -- *Ken Simpson*, CEO MailChannels Tel: *604-685-7488* www.mailchannels.com twitter.com/ttul* | *ca.linkedin.com/in/ksimpson -- ## 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/
