Hi Guys,
out of the blue, one particular exchange server generates tons of those
messages:
2018-06-07 12:26:17 H=(XXX) [XXX] X=TLSv1.2:DHE-RSA-AES128-SHA:128 CV=no
rejected AUTH LOGIN: blacklisted for bruteforce cracking attempt
generated by this ACL :
acl_check_auth:
drop message =
On 2018-05-30 09:16, Ian Zimmerman wrote:
> 2018-05-29 12:25:40 H=haskell.org [23.253.242.70]:51176 sender verify
> defer for : Could not complete
> sender verify callout: mail.haskell.org [23.253.242.70] :
> response to "RCPT TO:" was: 250
> 2.1.5 Ok
> 2018-05-29 12:25:40 H=haskell.org
On 06/07/2018 04:17 PM, Ian Zimmerman via Exim-users wrote:
> On 2018-05-30 09:16, Ian Zimmerman wrote:
>
>> 2018-05-29 12:25:40 H=haskell.org [23.253.242.70]:51176 sender verify
>> defer for : Could not complete
>> sender verify callout: mail.haskell.org [23.253.242.70] :
>> response to "RCPT
On 2018-06-07 16:44, Jeremy Harris wrote:
> >> 2018-05-29 12:25:40 H=haskell.org [23.253.242.70]:51176 sender verify
> >> defer for : Could not complete
> >> sender verify callout: mail.haskell.org [23.253.242.70] :
> >> response to "RCPT TO:" was: 250
> >> 2.1.5 Ok
> >> 2018-05-29 12:25:40
On Wed, 30 May 2018, Ian Zimmerman via Exim-users wrote:
I just turned on callout sender verify with the random option.
Strangely, the first (and only the first) connect from many domains
after that is temporarily rejected, although the callout seems to
succeed with a 250 status code. The log
It seems the only way to make exim with the -bd option _not_ become a
daemon, and _not_ disconnect from the controlling terminal, is to also
give it a -d option.
I need the foreground behavior to run exim under the supervisor daemon,
but I don't care for the verbose debugging output. How can I
