Re: [exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Sebastian Arcus via Exim-users
On 27/12/17 16:49, Jeremy Harris wrote: On 27/12/17 15:21, Sebastian Arcus via Exim-users wrote: Yes, a way to turn a defer into a hard fail is what I would need in this case. Am I correct in thinking that when the defer happens and the ACL processing is aborted, the DELAY gets skipped? 1)

Re: [exim] Possibly unclear logging after connection is closed by the far end during DELAY

2017-12-27 Thread Sebastian Arcus via Exim-users
On 27/12/17 17:00, Jeremy Harris wrote: On 27/12/17 16:24, Sebastian Arcus via Exim-users wrote: I've spotted this while investigating issues with DELAY in in acl's, in my other recent thread. It would seem that if a DROP acl has a long DELAY set, and if during that DELAY the remote end just

Re: [exim] Possibly unclear logging after connection is closed by the far end during DELAY

2017-12-27 Thread Jeremy Harris
On 27/12/17 16:24, Sebastian Arcus via Exim-users wrote: > I've spotted this while investigating issues with DELAY in in acl's, in > my other recent thread. It would seem that if a DROP acl has a long > DELAY set, and if during that DELAY the remote end just gets fed up and > closes the

Re: [exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Jeremy Harris
On 27/12/17 15:21, Sebastian Arcus via Exim-users wrote: > Yes, a way to turn a defer into a hard fail is what I would need in this > case. Am I correct in thinking that when the defer happens and the ACL > processing is aborted, the DELAY gets skipped? 1) Please trim your included text 2) Yes.

Re: [exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Jeremy Harris
On 27/12/17 16:13, Sebastian Arcus via Exim-users wrote: > Ok - no sooner did I send my last email to the list, that a series of > spurious connections attempts started on another email server I > administer. I have below the log extract with exim -bd > -d-all+resolver+dns+verify > > > 18213

Re: [exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Sebastian Arcus via Exim-users
On 27/12/17 12:58, Jeremy Harris wrote: On 27/12/17 12:39, Sebastian Arcus via Exim-users wrote: processing "drop"  5976   message: Reverse DNS record incorrect or missing  5976 check !condition = ${if eq{$received_port}{587}}  5976  =  5976 check !verify =

Re: [exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Sebastian Arcus via Exim-users
On 27/12/17 12:58, Jeremy Harris wrote: On 27/12/17 12:39, Sebastian Arcus via Exim-users wrote: processing "drop"  5976   message: Reverse DNS record incorrect or missing  5976 check !condition = ${if eq{$received_port}{587}}  5976  =  5976 check !verify =

Re: [exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Sebastian Arcus via Exim-users
On 27/12/17 13:57, Heiko Schlittermann via Exim-users wrote: Sebastian Arcus via Exim-users (Mi 27 Dez 2017 13:39:26 CET): …. Thank you for the suggestion. I think the following are the relevant lines of output: processing "drop" 5976 message: Reverse DNS record

Re: [exim] Some mails are queued, other are sent immediately

2017-12-27 Thread Lena--- via Exim-users
> From: Jeremy Harris > Could you do that with debug enabled? Using csh, I redirected debug output (-bd -q10m -d+all) to a file with >& (both stdout and stderr to the same file, some log lines might be broken and interspersed because of buffering). The file (compressed with bzip2) can be

Re: [exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Heiko Schlittermann via Exim-users
Sebastian Arcus via Exim-users (Mi 27 Dez 2017 13:39:26 CET): …. > Thank you for the suggestion. I think the following are the relevant lines > of output: > > > > processing "drop" > 5976 message: Reverse DNS record incorrect or missing > 5976 check !condition = ${if

Re: [exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Jeremy Harris
On 27/12/17 12:39, Sebastian Arcus via Exim-users wrote: > processing "drop" >  5976   message: Reverse DNS record incorrect or missing >  5976 check !condition = ${if eq{$received_port}{587}} >  5976  = >  5976 check !verify = reverse_host_lookup >  5976 looking up host name to

Re: [exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Sebastian Arcus via Exim-users
On 27/12/17 11:01, Jeremy Harris wrote: On 27/12/17 10:19, Sebastian Arcus via Exim-users wrote: Apologies for posting for the third time in three days. I have the following acl in acl_smtp_connect, which appears to be ignoring completely the "delay =" setting: drop message = Reverse DNS

Re: [exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Heiko Schlittermann via Exim-users
Sebastian Arcus via Exim-users (Mi 27 Dez 2017 11:19:11 CET): > Apologies for posting for the third time in three days. I have the following > acl in acl_smtp_connect, which appears to be ignoring completely the "delay > =" setting: You're welcome :) > drop message =

Re: [exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Jeremy Harris
On 27/12/17 10:19, Sebastian Arcus via Exim-users wrote: > Apologies for posting for the third time in three days. I have the > following acl in acl_smtp_connect, which appears to be ignoring > completely the "delay =" setting: > > drop message = Reverse DNS record incorrect or missing >  

[exim] Exim not obeying "delay = " in acl_smtp_connect

2017-12-27 Thread Sebastian Arcus via Exim-users
Apologies for posting for the third time in three days. I have the following acl in acl_smtp_connect, which appears to be ignoring completely the "delay =" setting: drop message = Reverse DNS record incorrect or missing ! condition = ${if eq{$received_port}{587}} ! verify