That’s still pretty cumbersome unfortunately. I’m somewhat familiar with fail2ban. What I’m looking for should be just the variables passed to the action line like:
I assume that’s just a GitHub request for Fail2ban configuration to be added to the <mailcow_root>/data/conf/ directory? Mucking around inside the docker container doesn’t sound like a good idea given the distribution.
Is there a way to move SOGo to it’s own IP or port? Looking through the logs I’m getting a LOT of mailcow UI attempts. I would love to lock that down some more at least. I see I can get to the Nginx config, but I would rather shut that all down on the firewall and eschew a proxy.