Author: Zbigniew Szalbot Date: To: exim-users Subject: Re: [exim] fatal bounces / cut off time
Hello,
2008/3/12, Phil Pennock <exim-users@???>: > On 2008-03-11 at 00:16 +0100, Zbigniew Szalbot wrote:
> > 2008/3/11, Phil Pennock <exim-users@???>:
> > > On 2008-03-10 at 18:14 +0100, Zbigniew Szalbot wrote:
> > > > When there is a fatal bounce for account example1@???, and
> > > > there comes another message which should be delivered to
> > > > example2@??? (same domain) by remote_smtp, the message
> > > > example2@ is immediately bounced (because of previous problems with
> > > > that domain).
>
>
> That's not what your logs show. They show that the new mail came in, a
> delivery attempt was made; that bounced, there was no recent record of a
> successful delivery, so the new mail was bounced too.
>
> There's a difference between "try once to confirm, then bounce" and
> "immediately bounce".
>
> If you think that some domains are doing this, per recipient, then
> create a new dnslookup Router; put it before the normal dnslookup
> router, add a "domains = yahoo.com" restriction (and adjust to restrict
> it to the domains you care about), add "no_more" and add
> "retry_use_local_part".
My question is more general though. In situations when I get
connection timeouts, I would like mail to be bounced after the retry
period passes. And when it does, I'd like exim to bounce only
particular email without affecting other emails to the same domain. So
each email should be queued for 4 days before it gets bounced. And I
would like this to happen not only for yahoo but for other domains. I
know it creates some overhead but I can live with that. However, this
applies only to timeouts, not to 5.5.4 or the like errors.
In reality I would simply like to save as many emails as possible
while I am working on getting unblocked. Thank you anyway!
