• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Manually add IP to fail2ban ip-table list

C

chris_cross

New Pleskian
I had the problem, that on one of my servers there I experienced unwanted mails, that could not be handled by the individual spam filter. As I wanted to exclude a bunch of IP from communication with the mail system I simply added the IP to "fail2ban-plesk-postfix" chain. I expected the IP to show up on the fail2ban list that plesk offeres so that it easily could get removed via the web interface, but my entries did not show up.

Is there a possibility to get IP´s manageable via the fail2ban GUI?

(of course I could use the blacklist function of the mail system, but then I still got traffic on my system)

Thanks

Chris
 
You must log in or register to reply here.

Similar threads

miagg
Resolved Backup Manager unable to back up banned IP addresses
Replies
5
Views
2K
miagg
miagg
I
Forwarded to devs Postfix fail2ban filter misses authentication failures
Replies
1
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
J
Question Fail2Ban exclude trusted IPs
Replies
0
Views
882
John W
J
bigbear67
Question Network routing issue after update (loss of default route source IP / DNS failure on Ubuntu 24.04)
Replies
0
Views
1K
bigbear67
bigbear67
I
Resolved Preventing bot brute force probes against Postfix/SMTP
Replies
5
Views
3K
iainh
I
Back
Top