Bug 2426440
| Summary: | fail2ban does not work with dovecot-2.4 logs | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kim Bisgaard <kim-rh> |
| Component: | fail2ban | Assignee: | Richard Shaw <hobbes1069> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 43 | CC: | anon.amish, hobbes1069, orion |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | fail2ban-1.1.0-15.fc43 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2026-01-09 17:21:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kim Bisgaard
2025-12-31 10:00:25 UTC
I tried pulling the new config into the build but now the internal testing fails so this has become a non-trivial problem. Bad luck :-( FEDORA-2025-5f4437e62e (fail2ban-1.1.0-15.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-5f4437e62e FEDORA-2025-5f4437e62e has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-5f4437e62e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5f4437e62e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. I note that the 'mdre-aggressive' has not been corrected. But otherwise all fine from here FEDORA-2025-5f4437e62e (fail2ban-1.1.0-15.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. |