Don't individually mail all fail2ban actions #124
Merged
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
Don't mail them individually to the destemail. The destemail setting is thus no longer used, but let's set it anyway to be clear where it will mail if you change the action back.
lukecyca
added a commit
that referenced
this pull request
Jan 6, 2014
Don't individually mail all fail2ban actions
|
Thanks! |
Closed
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.
As configured, every ban against the main fail2ban jails (sshd, apache, postfix) is individually mailed to the
admin_emailaddress. Each jail is also enumerated in ten “stopped”/“started” emails whenever fail2ban is restarted. By using theaction_shortcut instead ofaction_mwl, themail-whois-linesaction is not invoked and no individual email is sent.As the bans are still logged, the results are rolled up into the Logwatch email instead, and sent once together with all the other Logwatch notices.
This is the change I made to address issue #98, but I'm no expert so there might be a better method.