At 02:28 PM 11/7/2001 -0500, Dave C. wrote:
>On Wed, 7 Nov 2001, Jeff Hodge wrote:
>
>> At 06:11 PM 11/7/2001 +0100, Tamas TEVESZ wrote:
>> >On Wed, 7 Nov 2001, Jeff Hodge wrote:
>> >
>> > > How can you tell if a retry rule is working? Are the retries logged
>> > > anywhere? I do not think exim is retrying to send to a remote smtp
>> that is
>> > > down. Do I also need to have a queue runner? I only start exim
with
>> -bd
>> > > option. My retry rules are the default setting.
>> > >
>> > > * * F,2h,15m; G,16h,1h,1.5; F,4d,8h
>> >
>> >exinext <domain> should give you some insight, also exim_dumpdb on the
>> >retry database can sched some light.
>> >
>> >--
>>
>> Tamas,
>> Thanks for your reply. Here is the output of exinext and the db dump
>>
>> exinext hilltoppress.com
>> Deliver: mail.hilltoppress.com [66.148.140.83] error 110: Connection
timed
>> out
>> first failed: 07-Nov-2001 09:11:11
>> last tried: 07-Nov-2001 09:11:11
>> next try at: 07-Nov-2001 09:26:11
>>
>>
>> exim_dumpdb /var/spool/exim retry
>> T:mail.hilltoppress.com:66.148.140.83 110 77 Connection timed out
>> 07-Nov-2001 09:11:11 07-Nov-2001 09:11:11 07-Nov-2001 09:26:11
>>
>> It does not look like exim is trying to resend the message. There is
>> nothing in the log files to show that it tried to send the message
again.
>> Is a queue runner responsible for the retries?
>> Thanks for your time.
>
>What time was it that you ran that command?
>
>It should try againat of after 9:26, and yes, only by a queue runner..
>
I ran the commands about 2:00 today, but from the replies from this group,
I think my problem is that I am not running exim with a queue runner and
that is why my message are not being retried.
