> Fail2ban is not useful in your case since it only counts logins from ip
> addresses, not blocking user names
Doesn't fail2ban count what it's taught to count.? If there is some distinct
log messages you could regex for, it's an option.
(On a Debian box you could check /etc/fail2ban/filter.d for
On 25/07/2011 22:07, tonjg wrote:
>
>
> Tom Hendrikx wrote:
>>
>> dovecot 2.x has an automatic backoff system (see auth_failure_delay
>> config option).
>>
>> When you're not interested in upgrading
>>
> I think with my old server upgrading to 2.x is not an option so I'll have to
> check out fai
Tom Hendrikx wrote:
>
> dovecot 2.x has an automatic backoff system (see auth_failure_delay
> config option).
>
> When you're not interested in upgrading
>
I think with my old server upgrading to 2.x is not an option so I'll have to
check out fail2ban. It looks a bit complicated though...
I'l
On 25/07/11 20:05, tonjg wrote:
>
> I'm using dovecot 1.1.8 on a raq4 server running centos 4.8
> Is it possible to set a time delay between all dovecot pop3-logins? say 20 -
> 30 seconds for example?
> My reason is I want to thwart the constant login attempts from hackers
> hunting for an open re
I'm using dovecot 1.1.8 on a raq4 server running centos 4.8
Is it possible to set a time delay between all dovecot pop3-logins? say 20 -
30 seconds for example?
My reason is I want to thwart the constant login attempts from hackers
hunting for an open relay. It's no good blocking the ip address b
