On 8/27/2017 4:49 PM, Jeremy Harris wrote:
> On 27/08/17 17:54, John Schmerold via Exim-users wrote:
>> Several times in the past week, I have had message delivery fail:
>> 2017-08-27 09:50:54 1dlytj-0006RW-4r == support@??? R=external
>> T=remote_smtp defer (111): Connection refused
>> 2017-08-27 09:50:54 1dlytj-0006RW-4r ** support@???: retry
>> timeout exceeded
>> If I wait an hour or so and resend the message it is sent. Isn't this
>> supposed to accomplish the same thing:
>> begin retry
>> katy.com * F,2h,15m; G,16h,1h,1.5; F,4d,6h
>> * * F,2h,15m; G,16h,1h,1.5; F,1d,6h
>>
>> Where am I going wrong?
> Without knowing the state of your retry database we can't tell.
>
> Try playing with
>
>
> http://exim.org/exim-html-current/doc/html/spec_html/ch-exim_utilities.html#SECTfinindret
>
> but bear in mind that it is referencing data that is dynamically
> modified by exim operations.
Hmm, if this is indicative of a corrupt retry database, perhaps I should
assume that other corruptions exist and do a "rm -f
/var/spool/exim/db/*" after shutting down Exim.
Any downsides - other than losing greylist data?
