Re: [exim] Retry rule of NDR based on error

Hi, Todd Lyons tly...@ivenue.com (Mo 12 Mai 2014 18:08:32 CEST): On Sun, May 11, 2014 at 5:10 AM, Thomas Hommers thomas.homm...@ebalu.com wrote: Actually that was not what i meant, my question should be: How do i make exim droping an email （NDR） on 5xx error instead of freezing and retry？

Re: [exim] Retry rule of NDR based on error

Hi Heiko, i would like to have it based on the reason the NDR was created, not the error that cause the NDR to freeze during it's delivery. Can this be achieved with the retry rule and error condition as you mentioned? Thanks, Thomas On Heiko Schlittermann h...@schlittermann.de, May 13, 2014

Re: [exim] Retry rule of NDR based on error

On 10/05/14 04:14, Thomas Hommers wrote: my exim server acts as gateway, some email is rejected as spam by the destination server and exim therefore creates a NDS (bounce) message. Because a lot of the spam senders won't send with a legit sender address, exim continues trying to send the NDR

Re: [exim] Retry rule of NDR based on error

Hi Jeremy, thank you very much for your extensive reply! I will definitely look into cutthrough routing, then I won't need to deal with those NDR anymore. What if i can't implement cutthrough routing. Is there any way for exim to see for what reason an NDR was created and apply a special retry

Re: [exim] Retry rule of NDR based on error

On Sun, May 11, 2014 at 5:10 AM, Thomas Hommers thomas.homm...@ebalu.com wrote: Actually that was not what i meant, my question should be: How do i make exim droping an email （NDR） on 5xx error instead of freezing and retry？ If exim gets a 5xx when trying to send an NDR, then it freezes the

Re: [exim] Retry rule of NDR based on error

Hi, We actually implement similar behavior in our fallback queues, which is for remote servers that respond slowly or intermittently. The method we used is in the Exim system filter, and is simple as this: if error_message and not first_delivery and $message_age is above 7200 then

Re: [exim] Retry rule of NDR based on error

Hi Todd, thanks for your comment. Actually that was not what i meant, my question should be: How do i make exim droping an email （NDR） on 5xx error instead of freezing and retry？ regards Thomas On Todd Lyons tly...@ivenue.com, May 11, 2014 1:51 AM wrote: If the NDR gets a 5xx response (i.e.

Re: [exim] Retry rule of NDR based on error

If the NDR gets a 5xx response (i.e. user doesn't exist, rejected as spam, etc) exim should then freeze the NDR. Your question is actually If I get a temporary error (a 4xx response), how do I force exim to blackhole or redirect the message to some box I can later inspect? I've not done this nor

[exim] Retry rule of NDR based on error

Hi, my exim server acts as gateway, some email is rejected as spam by the destination server and exim therefore creates a NDS (bounce) message. Because a lot of the spam senders won't send with a legit sender address, exim continues trying to send the NDR even tough the destination rejects the

[exim] Exim retry rule configuration

Hello, We are using Exim version 4.69. I have some questions about the exim retry rule configuration. We are using an exim server as a secondary MX for a domain abc.com, and used default retry rule for the domain abc.com as follows: abc.com * F,2h,15m; G,16h,1h,1.5; F,4d,8h; I think we have

[exim] Retry rule

Hi, I have a very simple retry rule: some.domain.com * My understanding of retry rules suggests that any mail to this domain will be dumped after the first attempt fails. But this is not happening. Mail is queued as normal and does obey the global rule: * * F,2h,15m; G,16h,1h,1.5; F,2d,6h

[exim] retry rule

Hello list How can i make sure that a retry rule for one custum domain is working. I use exim 4.63 on debian etch as a relay gateway. The default retry rule will drop undelivereble mail after 4d. I now have one relay domain that are offline for unspesified time and i need to keep all the mail

Re: [exim] retry rule

How can i make sure that a retry rule for one custum domain is working. I use exim 4.63 on debian etch as a relay gateway. The default retry rule will drop undelivereble mail after 4d. I now have one relay domain that are offline for unspesified time and i need to keep all the mail until

[exim] retry rule in exim.conf question

hi, if in exim.conf I have several retry rule in exim configuration files: * * F,2h,10m; G,10h,1h,3; F,2d,6h * * F,2h,15m; G,10h,1h,1.5; F,2d,6h * * F,2h,15m; G,16h,1h,1.5; F,4d,8h which one will be run first ? and i wonder whether the second and the third rule will be executed or not...

Re: [exim] retry rule lost_connection or tls_required

On Sun, 15 Oct 2006, Andre van der Walt wrote: when trying to set a retry rule for lost_connection or tls_required as follows: * tls_required F,2h,15m; F,1d,4h * lost_connectionF,2h,15m; F,1d,4h you get the following errors when doing exim -bV

Re: [exim] retry rule lost_connection or tls_required

On 10/17/06, Philip Hazel [EMAIL PROTECTED] wrote: It's amazing that nobody noticed this stupid bug before. The simple patch that fixes it is below. A feature that is most probably not used much yet. Thanks for the patch, can confirm that everything is working now without any errors :) Andre

Re: [exim] retry rule lost_connection or tls_required

Andre van der Walt wrote: hi, when trying to set a retry rule for lost_connection or tls_required as follows: * tls_required F,2h,15m; F,1d,4h * lost_connectionF,2h,15m; F,1d,4h you get the following errors when doing exim -bV 2006-10-15 21:38:53