I've followed one of the pages on line specifically for installing fail2ban on
Centos 7 and all looks fine.
I've added a fail regex to /etc/fail2ban/filter.d/exim.conf as suggested on
another page:
\[\]: 535 Incorrect authentication data
which appears to be successfully matchnig lines i
> I've added a fail regex to /etc/fail2ban/filter.d/exim.conf as suggested on
> another page:
The standard exim.conf already has a 535 filter. Was that not working
for you?
>
>\[\]: 535 Incorrect authentication data
>
> which appears to be successfully matchnig lines in /var/log/exi
On Friday 19 April 2019 15:19:26 Pete Biggs wrote:
> > I've added a fail regex to /etc/fail2ban/filter.d/exim.conf as suggested
> > on another page:
>
> The standard exim.conf already has a 535 filter. Was that not working
> for you?
I was following the instructions as shown on the page. I did fi
I find csf/lfd much easier to configure and can be used in combination with
fail2ban.
Gary Stainburn wrote:
>I've followed one of the pages on line specifically for installing fail2ban on
>Centos 7 and all looks fine.
>
>I've added a fail regex to /etc/fail2ban/filter.d/exim.conf as suggested
On 4/19/2019 5:30 AM, Gary Stainburn wrote:
I've followed one of the pages on line specifically for installing fail2ban on
Centos 7 and all looks fine.
Which page? It would help to see what they advised.
___
CentOS mailing list
CentOS@centos.org
htt
>
> The event that triggers the ban does complete as normal, which is what I
> would
> expect as the ban is triggered by the log entry which is *after* the failed
> attempt.
>
> However, after the /var/log/fail2ban.log showed the IP as banned, I continue
> to see entries in /var/log/exim/ma
Hi,
I am running the below command on CentOS Linux release 7.6.1810 (Core)
# df -hT --total
Filesystem Type Size Used Avail Use% Mounted on
/dev/xvda1 xfs 150G 8.0G 143G 6% /
devtmpfs devtmpfs 7.8G 0 7.8G 0% /dev
tmpfs tmpfs 7.8G 0 7.8G 0%
7 matches
Mail list logo
