On Fri, 18 Jul 2014, Pressy wrote:
actual i can't seemed to reproduce the authentication failure - type
message. I'm not sure if this caused by my ldap-backend for user
authentication.
For all the different failure message that cyrus/imaps, I also use a
more complex failregex.
Package: fail2ban
Version: 0.8.6-3wheezy3
Severity: normal
Dear Maintainer,
with the last update on cyrus-imap.conf secure connections (imaps) are ignored.
Changing the daemon line
from:
_daemon = (?:cyrus/)?(?:imapd?|pop3d?)
to:
_daemon = (?:cyrus/)?(?:imap(d|s)?|pop3(d|s)?)
has fixed
On Fri, 18 Jul 2014, pressy wrote:
Package: fail2ban
Version: 0.8.6-3wheezy3
Severity: normal
Dear Maintainer,
with the last update on cyrus-imap.conf secure connections (imaps) are
ignored. Changing the daemon line
from:
_daemon = (?:cyrus/)?(?:imapd?|pop3d?)
to:
_daemon =
here is a sample logfile:
Jul 17 22:54:54 derry cyrus/imaps[7568]: badlogin: serafinat.xx
[192.168.xx.xx] plain [SASL(-13): user not found: Password verification
failed]
Jul 17 22:54:59 derry cyrus/imaps[7568]: badlogin: serafinat.xx
[192.168.xx.xx] plaintext pressy SASL(-13):
4 matches
Mail list logo
