Adding IP address to logs for 535 LOGIN errors, to use with fail2ban #301
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
msimerson
approved these changes
Aug 19, 2021
|
great description of what it does, thanks for the contribution. |
|
You're most welcome. Always nice to be able to scratch my own itch, and help others to do the same. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on the idea and patch linked from here: https://www.linkedin.com/pulse/howto-add-fail2ban-support-qpsmtpd-authentication-failures-andrew-pam/
Basically, just add the IP address to the log for other tools (in my case fail2ban) to parse and ban IPs that fail to authenticate.
This is ever so slightly different, as the link above is 5 years old. I tried this out directly against 0.94-4 in Debian Buster, then replicated the one-line change against current master.