[exim] problems with retry logic

Top Page
Delete this message
Reply to this message
Author: Pavel Gulchouck
Date:  
To: exim-users
Subject: [exim] problems with retry logic
Hi,

I have two problems with retries, and I think its are relative.
I did not found any hints in the spec about this.

I have a default retry line:

# Domain               Error       Retries
# ------               -----       -------
*                      *           F,2h,15m; G,16h,1h,1.5; F,4d,6h


1. When many undelivirable messages to the single email exists in the
queue, exim makes only single delivery attempt each time. Messages
are very old (8 days and older), so each time exim deletes only one
message from the queue, and says "retry time not reached" about
other messages to the same address. IMHO more reasonable behavior
is to delete (or freeze and then delete) all messages to this
destination older then 4 days.
Current queue state:
root@hamster:~>mailq | head -5
 6d  1.8K 1FZbYM-000IDB-Hk <>
          frenzy2008@???


 6d  1.8K 1FZbrw-000HzZ-Up <>
          frenzy2008@???
root@hamster:~>exim -v -q 1FZbYM-000IDB-Hk 1FZbrw-000HzZ-Up
LOG: queue_run MAIN
  Start queue run: pid=47160
delivering 1FZbrw-000HzZ-Up (queue run pid 47160)
LOG: retry_defer MAIN
  == frenzy2008@??? routing defer (-51): retry time not reached
delivering 1FZbYM-000IDB-Hk (queue run pid 47160)
LOG: retry_defer MAIN
  == frenzy2008@??? routing defer (-51): retry time not reached
LOG: queue_run MAIN
  End queue run: pid=47160



2. Sometimes I see following life of the message:

root@hamster:~>grep 1FbcLg-0003Cg-3G /var/log/maillog
May 4 14:50:24 hamster exim[12318]: 1FbcLg-0003Cg-3G <= netmon@??? H=f16.pfts.com [213.133.160.25] P=esmtps X=TLSv1:AES256-SHA:256 S=682 id=L66pOY9UXEX3kVSZ@??? from <netmon@???> for alarm@???
May 4 14:50:25 hamster exim[12319]: 1FbcLg-0003Cg-3G == its@??? <alarm@???> R=dnslookup T=remote_smtp defer (-44): SMTP error from remote mail server after RCPT TO:<its@???>: host relay2.carrier.kiev.ua [193.193.193.119]: 450 4.7.1 <its@???>... No route back to <netmon@???>, best MX unavailable. (relay2.pfts.com) RCPT TO: 250 Accepted
May 4 15:10:38 hamster exim[13981]: 1FbcLg-0003Cg-3G Completed

No delivery, no bounces, no retries. :-(
But it was successful delivery before it:

May 4 14:49:05 hamster exim[12177]: 1FbcKP-0003AP-7k <= netmon@??? H=f16.pfts.com [213.133.160.25] P=esmtps X=TLSv1:AES256-SHA:256 S=796 id=PY5DVVTlBPaawtFQ@??? from <netmon@???> for alarm@???
May 4 14:49:06 hamster exim[12191]: 1FbcKP-0003AP-7k => its@??? <alarm@???> F=<netmon@???> R=dnslookup T=remote_smtp S=820 H=happy.kiev.ua [193.109.241.145] X=TLSv1:AES256-SHA:256
May 4 14:49:06 hamster exim[12191]: 1FbcKP-0003AP-7k Completed

I'm afraid delivery was not retried because of failing in the
delivery to this address in the past. Is it possible? Or, may be,
it is wrong configuration? What config parameters should I check?

Exim 4.60.

Thanks.

-- 
                                Lucky carrier,
                                                  Pavel.