Search results

Disable Amavis / SpamAssassin Fully uninstall “Plesk Email Security” from the Plesk UI In master.cf: make sure no Amavis pipes are left Restart postfix and rspamd to avoid conflicts ️ 2. Enable Rspamd Milter in Postfix Open your main.cf file: sudo nano /etc/postfix/main.cf Add the...

Hi @Daveo , hi all, as a quick update regarding the “next steps” after parallel operation and testing: We’ve now fully migrated to Rspamd in production and have completely removed Amavis and SpamAssassin from our mail stack. The current mail filtering setup now includes: Rspamd 3.12...

Hi everyone, @Daveo as requested, I've documented the full installation process of Rspamd on Plesk, running it in parallel with Amavis/SpamAssassin. The guide includes: repository setup (incl. Redis separation and ARM/i386 fix), postfix milter configuration without breaking Plesk’s DKIM/DMARC...

I've recently put Rspamd 3.12 into full production as a complete replacement for Amavis + SpamAssassin on my Plesk server (Ubuntu 22.04, Obsidian 18.0.70) – natively installed, without Docker or containerization. Current Setup: Postfix + Dovecot still managed through Plesk Rspamd with Redis...

Thanks for your input – much appreciated! I totally agree with you: SpamAssassin can be extremely powerful when heavily customized. I’ve also maintained a fairly extensive setup over the years with custom rules in 50-user, Razor, Pyzor, DNSBL tuning, and even DKIM/ARC scoring workarounds. So...

Hi everyone, I'm planning to switch from the default Plesk Email Security stack (Amavis, SpamAssassin 3.x, Pyzor, Razor, etc.) to a more modern and efficient solution based on Rspamd 3.12 on my Ubuntu 22.04 server. The decision comes mainly due to: a massive increase in spam recently, with...

Hi everyone, I'm running a Plesk server using the free Plesk Email Security extension, which includes Amavis and SpamAssassin. I’ve also installed ClamAV manually, and it's working perfectly within the current mail pipeline. To further reduce spam and bot traffic, I now plan to add Greylisting...

Thank you, then I will also apply the Apache variant.

I’m planning to make a third attempt next week to install ModSecurity under Plesk. During the setup, there’s an option to choose whether ModSecurity should be applied to Nginx or Apache. Since I’m using Nginx as a reverse proxy in front of Apache, it’s unclear which option I should select.

Unfortunately, not yet. The first time I tried it, it worked for a short time, but then ModSecurity stopped logging, and after uninstalling it, NGINX also stopped working, so I had to run my websites on Apache for a while. The second time I tried it, a month ago, it worked better, and...

I have now blocked CN, RU, ID, PH, KR, TH, VN, MY, IN . This has helped. Recently, however, I've also noticed a sharp increase in attacks on my server from the US. I hope I can continue to manage this with fail2ban so I don't have to add US to the list.

I also changed port 22, which helps against targeted 22 attacks but not against port scans looking for SSH access. I also blocked SSH access using a user/password combination. You can only log in to my server with keys!

Thanks for your good recommendation from Danami Juggernaut. But at the moment, it seems to be taking too much time for me to get it working. I'm about to go on a long trip and can only work on this solution more intensively after I return. In the meantime, I'm blocking all countries from which...

Thank you for all your valuable advice! Fail2Ban has now banned 1600 IPs and as I blocked countries with the most attackers now the attacks are slowing down to two to four each hour. I will test danami, as @learning_curve recommended. I am not sure, whether I could follow the recommendation by...

Hello everyone, I’m running a Plesk panel that has been under a massive brute-force attack for some time. The login attempts are happening non-stop from globally distributed IPs, targeting users like admin, root, and even custom usernames. I have already implemented the following security...

Thank you for your quick response! Unfortunately, Fail2Ban didn’t work because it couldn’t find any IPs in the ModSecurity audit log files, and ModSecurity itself stopped logging unexpectedly. As a result, I had to remove it again. Additionally, switching from the selected Apache rule set (2.9)...

Hello everyone, I have successfully installed ModSecurity with NGINX on my Plesk server. Now, I want to use Fail2Ban to permanently block IPs of attackers that ModSecurity identifies. However, after installation, I noticed that the configuration files for ModSecurity were missing in Fail2Ban...

I repaired it now by myself. To help others here is a step-by-step-approach: 1. ls -alh /etc/nginx/modsecurity.d/rules/owasp_modsecurity_crs_4-plesk/ => No rules have been installed. 2. nginx -V 2>&1 | grep -o with-http_modsecurity_module => no module installed also available 3...

So, i tried to solve it by myself. The plesk db contains the table MariaDB [emailsecurity]> DESCRIBE stats_accounts; +-----------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra |...

Up to now every hour the corresponding cron-task for Plesk Email Security extension stops with the error as mentioned above. Please advice a.s.a.p