On Mon, Oct 17, 2022 at 2:12 PM Charles Dennett <cdenn...@gmail.com> wrote:
> > I've been testing f2b over the past few days and I can now make it fail > on demand. By that I mean the fail2ban-server process uses 100% of a > cpu and becomes unresponsive and will not respond to fail2ban-client or > process any other log entries (apache, sshd, etc.) whenever it attempts > to process a dovecot log entry. > > This will happen if I use the latest 1.0.1 package. However, if I use > that but replace the doveconf.conf filter with the one from an earlier > version (I used the one from my last fedora 35 backup) everything works > fine. So, I would hazard a guess that something in the regex's in the > newest dovecot.conf file is the issue. I won't pretend to even begin to > understand them. They are quite complex to me. > > So for now I will use the older dovecot.conf file. If someone wants me > to test an updated version of dovecont.conf, I'd be glad to do that. > If you can, please file an issue upstream and let me know what the URL is. Include as much info as you're able, especially any relevant log file entries. https://github.com/fail2ban/fail2ban/issues Thanks, Richard
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
