Recent content by Jürgen_T

Thanks for your question. At the moment I don’t provide a separate step-by-step guide beyond what is already described in this thread and in the linked blog article. The setup involves several manual decisions and a solid understanding of Rspamd and the Plesk mail stack, and it was never...

Maybe my article will help: RSPAMD and Plesk

In my previous setup, DKIM was still handled by Plesk. Configuring it was a bit tricky, especially when using 2048-bit keys, whereas the old 1024-bit keys worked without any issues. In the meantime, I’ve removed the entire Plesk email stack (Amavis (comes with Plesk-E-Mail-Security) , Postfix...

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!