On 6 May 2019, at 02:10, Lefteris Tsintjelis <le...@spes.gr> wrote: > On 6/5/2019 9:42, @lbutlr wrote: >> On 4 May 2019, at 15:52, Lefteris Tsintjelis <le...@spes.gr> wrote: >>> Would be great to consider its future adoption and if possible to take it >>> even further to interact with postscreen. >> Why would this be a good thing for postfix to do? >> There are already plenty of tools that generate block lists for the various >> types of firewalls out there, and they do not require patching postfix. >> SSHGuard and Fail2Ban are two that seem to work very well. > > SSHguard is similar but only for ssh, not for postfix.
SSHGuard can be used to block anyone who tries to get into your system. It is not limited to SSH. It even can work without a firewall. > Fail2ban and equivalent log parsers are just too resource hungry, No they aren't. > messy and more time consuming to maintain Sounds like you are parting some false information others fed you. There is nothing to maintain, and they run silently and take no time at all. > blacklistd is offering simplicity, central management, extreme speed compared > to any log parser with minimal resources. There is no comparison really > between log parsers and balcklistd or SSHguard. If you say so. I've used both shgiard and fail2ban and have had no complaints or issues once they are configured. And they both offer a variety of configuration options. -- When we woke up that morning we had no way of knowing that in a matter of hours we'd changed the way we were going. Where would I be now? Where would I be now if we'd never met? Would I be singing this song to someone else instead?
