[exim] exim rety time problem with greylisting

トップ ページ
このメッセージを削除
このメッセージに返信
著者: Michael Brunner
日付:  
To: exim-users
題目: [exim] exim rety time problem with greylisting
Hi

I have a cpanel server with exim. A customer try to send a mail to another
server which is using greylisting.

In exim.conf I have the retry time configured, that during the first 2 hours,
eximt should retry every 15min to deliver the mail.

* * F,2h,15m; G,16h,1h,1.5; F,4d,8h

But when exim realize, that the other server is often "temporary down", which
means the other server gives the error 451 back (greylisting), then exim ignores
my retry time which I configured and just wait very long. Here is an example:

2009-09-01 23:20:17 1Miam1-0001jl-JF <= Info@???
H=84-72-143-74.dclient.xxxxxxx.ch ([10.0.1.3]) [84.75.148.74] P=esmtpsa
X=TLSv1:AES128-SHA:128 A=fixed_plain:info+xxxxxxxxx.ch S=1124
id=90126716-7D8A-4541-8A43-5AF7B65FD45F@??? T="Konten"
2009-09-01 23:20:17 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc
1Miam1-0001jl-JF
2009-09-01 23:20:21 1Miam1-0001jl-JF SMTP error from remote mail server after
RCPT TO:<info@???>: host mx01.hostingcompany.ch [134.132.236.15]:
451-134.132.238.138 is not yet authorized to deliver mail from\n451
<Info@???> to <info@???>. Please try later.
2009-09-01 23:20:24 1Miam1-0001jl-JF SMTP error from remote mail server after
RCPT TO:<info@???>: host mx01.hostingcompany.ch [194.150.248.33]:
451-134.132.238.138 is not yet authorized to deliver mail from\n451
<Info@???> to <info@???>. Please try later.
2009-09-01 23:20:24 1Miam1-0001jl-JF SMTP error from remote mail server after
RCPT TO:<info@???>: host mx02.hostingcompany.ch [194.150.249.34]:
451-134.132.238.138 is not yet authorized to deliver mail from\n451
<Info@???> to <info@???>. Please try later.
2009-09-01 23:20:24 1Miam1-0001jl-JF == info@??? R=lookuphost
T=remote_smtp defer (-44): SMTP error from remote mail server after RCPT
TO:<info@???>: host mx02.hostingcompany.ch [194.150.248.34]:
451-134.132.238.138 is not yet authorized to deliver mail from\n451
<Info@???> to <info@???>. Please try later.
2009-09-03 01:17:52 1Miam1-0001jl-JF SMTP error from remote mail server after
RCPT TO:<info@???>: host mx01.hostingcompany.ch [134.132.236.15]:
451-134.132.238.138 is not yet authorized to deliver mail from\n451
<Info@???> to <info@???>. Please try later.
2009-09-03 01:17:55 1Miam1-0001jl-JF SMTP error from remote mail server after
RCPT TO:<info@???>: host mx01.hostingcompany.ch [194.150.248.33]:
451-134.132.238.138 is not yet authorized to deliver mail from\n451
<Info@???> to <info@???>. Please try later.
2009-09-03 01:17:55 1Miam1-0001jl-JF SMTP error from remote mail server after
RCPT TO:<info@???>: host mx02.hostingcompany.ch [194.150.249.34]:
451-134.132.238.138 is not yet authorized to deliver mail from\n451
<Info@???> to <info@???>. Please try later.
2009-09-03 01:17:55 1Miam1-0001jl-JF == info@??? R=lookuphost
T=remote_smtp defer (-44): SMTP error from remote mail server after RCPT
TO:<info@???>: host mx02.hostingcompany.ch [194.150.248.34]:
451-134.132.238.138 is not yet authorized to deliver mail from\n451
<Info@???> to <info@???>. Please try later.
2009-09-03 01:17:55 cwd=/var/spool/exim 7 args: /usr/sbin/exim -t -oem -oi -f <>
-E1Miam1-0001jl-JF
2009-09-03 01:17:55 1Miz5P-0004Pl-KU <= <> R=1Miam1-0001jl-JF U=mailnull P=local
S=1388 T="Warning: message 1Miam1-0001jl-JF delayed 24 hours"
2009-09-03 01:24:47 1Miam1-0001jl-JF == info@??? routing defer (-51):
retry time not reached
2009-09-03 01:25:38 1Miam1-0001jl-JF == info@??? routing defer (-51):
retry time not reached
2009-09-03 01:26:03 1Miam1-0001jl-JF == info@??? routing defer (-51):
retry time not reached
2009-09-03 01:32:05 1Miam1-0001jl-JF == info@??? routing defer (-51):
retry time not reached
2009-09-03 02:38:25 1Miam1-0001jl-JF == info@??? routing defer (-51):
retry time not reached
2009-09-03 03:28:56 1Miam1-0001jl-JF == info@??? routing defer (-51):
retry time not reached
2009-09-03 05:28:53 1Miam1-0001jl-JF == info@??? routing defer (-51):
retry time not reached
2009-09-03 06:25:36 1Miam1-0001jl-JF == info@??? routing defer (-51):
retry time not reached

How can I configure exim, that it ignores this database and just retry like
configured?

Best Regards
Michael BrunnerFrom eximX0902w@??? Fri Sep 04 08:03:12 2009
Envelope-to: exim-users@???
Received: from mxa.outb.inboxlogistics.com ([203.211.140.222]:50256)
    by tahini.csx.cam.ac.uk with esmtp (Exim 4.69)
    (envelope-from <eximX0902w@???>) id 1MjSoz-0001eZ-78
    for exim-users@???; Fri, 04 Sep 2009 08:03:12 +0100
Received: from 218-214-70-24.people.net.au ([218.214.70.24]
    helo=[192.168.0.188])
    by mxa.inb.inboxlogistics.com with esmtpsa (TLSv1:AES256-SHA:256)
    (Exim 4.69) (envelope-from <eximX0902w@???>)
    id 1MjSop-00067Z-D6
    for exim-users@???; Fri, 04 Sep 2009 17:02:55 +1000
Message-ID: <4AA0BB93.8080104@???>
Date: Fri, 04 Sep 2009 17:02:43 +1000
From: Ted Cooper <eximX0902w@???>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: exim-users@???
References: <21583e350909030658w1c924bf6wf1c58d5d9d6ccacd@???>
In-Reply-To: <21583e350909030658w1c924bf6wf1c58d5d9d6ccacd@???>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.7 (---)
X-Spam-Score: -2.0 (--) 
X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL=0.452, BAYES_00=-1.5,
    EXIM_EXP_VAR=-1 autolearn=ham version=3.1.8
Subject: Re: [exim] mysql retry times
X-BeenThere: exim-users@???
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: exim-users@???
List-Id: A user list for the exim MTA <exim-users.exim.org>
List-Unsubscribe: <http://lists.exim.org/mailman/listinfo/exim-users>,
    <mailto:exim-users-request@exim.org?subject=unsubscribe>
List-Archive: <http://lists.exim.org/lurker/list/exim-users.html>
List-Post: <mailto:exim-users@exim.org>
List-Help: <mailto:exim-users-request@exim.org?subject=help>
List-Subscribe: <http://lists.exim.org/mailman/listinfo/exim-users>,
    <mailto:exim-users-request@exim.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Sep 2009 07:03:12 -0000


Thomas kinghorn wrote:
> Afternoon All.
>
> Is it possible to have a mysql query in the retry configuration
> so that different domains have various different retry configurations?


When doing exactly what you tried - Short answer, no. Only the first
part of the line expanded - the single part address list. The rest of
line has a specific format as specified in:

http://docs.exim.org/current/spec_html/ch32.html

However, you could make the a table that matched up every domain to the
retry rule you wanted. Maybe.

The following was produced at exactly 1 minute to 5 (end of work) when I
was thinking of beer and what I was going to do for the weekend.

ie a table like .
domain varchar
retryline int

a query like
MYSQLRETRY1=SELECT domain FROM domretry WHERE retryline = 1 AND domain =
${mysqlescapethingy{$domain}}
MYSQLRETRY2=SELECT domain FROM domretry WHERE retryline = 2 ....

and a retry table that looked
${lookup{mysql{MYSQLRETRY1}} * F,4d,6h
${lookup{mysql{MYSQLRETRY2}} * F,7d,2h

Maybe? I haven't really thought about this :P