• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Issue Fail2ban parameters

xemorytr

Basic Pleskian
Server operating system version
Ubuntu 22.04.2 LTS
Plesk version and microupdate number
Version 18.0.50 Update #2
Hello everyone ,
I need information about fail2ban parameters and plesk-postfix to improve heem and how it can be done.

I think that if the feature I mentioned comes in the new update, it may be a better solution for everyone.

Invalid password for .+ by ([0-9a-f\.:]+)
Invalid password by ([0-9a-f\.:]+)
warning: .*\[([0-9a-f\.:]+)\]: SASL .+ authentication failed: (?!.*Connection lost to authentication server).+
warning: non-SMTP command from .*\[([0-9a-f\.:]+)]:.+
NOQUEUE: reject: RCPT from \[([0-9a-f\.:]+)].+Protocol error.+
-login: Disconnected.+ \(auth failed, .+\): user=.*, method=.+, rip=([0-9a-f\.:]+),
-login: Aborted login.+ \(auth failed .+\): user=.+, rip=([0-9a-f\.:]+), lip.+
-login: Aborted login.+ \(tried to use disallowed .+\): user=.+, rip=([0-9a-f\.:]+), lip.+
webmail.+ Login from '([0-9a-f\.:]+)' for user .+ might not have worked
([0-9a-f\.:]+) "GET \/webmail\/.* HTTP.+" 403 .+

These rules really need to be.

What steps can be followed for this?
Thank you.
 
Back
Top