1

Topic: Fail2ban locking some users out

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.6
- Linux/BSD distribution name and version: Ubuntu 14.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? No
- Related log if you're reporting an issue: /var/log/dovecot.log
====

Hello,

Since the update to iRedMail 0.9.6 some users get locked out. In the dovecot.log this entry is appearing:

Feb 22 15:15:39 imap-login: Info: Disconnected (no auth attempts in 0 secs): user=<>, rip=*.*.*.*, lip=*.*.*.*, TLS: Disconnected, session=<yWOPIR9J6AAlGJmz>

Are their clients misconfigured? Or is it a problem of the client software (K-9)? And what could they change to stop the server locking them out?

Thanks in advance!

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Fail2ban locking some users out

A bug in iRedMail's fail2ban config file.

Please open file /etc/fail2ban/filter.d/dovecot.iredmail.conf, remove line below:

            \(no auth attempts in .* rip=<HOST>

Then restart or reload Fail2ban service.

3

Re: Fail2ban locking some users out

Wasn't it this line which was added with the last update?

4

Re: Fail2ban locking some users out

It turns out it's not so good, because some MUAs will produce these error message.

5

Re: Fail2ban locking some users out

Ok, thanks for the info!