Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We value your experience with Plesk during 2025 Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025. Please take this short survey: https://survey.webpros.com/
On Plesk for Linux mod_status is disabled on upgrades to improve Apache security. This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.
It seems that issue is back again. I've just solved by giving SSH access to the account. It seems fetch url just wraps URLs with this script and puts it into user's own crontab.
Is it possible to enable SA server-wide? My initial assumption was that "Turn on server-wide SpamAssassin spam filtering" was meant for that exactly purpose. It's quite counter-intuitive to enable critical email feature for each individual mailbox.
Test3.eml (used for CLI check) is the actual message in my RoundCube inbox. X-Spam headers are missing from ALL emails.
Actually, I'm afraid SpamAssasin is NOT invoked at all, as I can't see any messages marked as spam, despite it's enabled in Plesk server wide (see screenshot attached). Did...
Hey @Kaspar ,
Thanks for the suggestion. I've run the same email through the local test you've suggested and I can clearly see my custom header:
# spamassassin -d -t -L ./Test3.eml
Sep 9 19:59:09.041 [2503663] warn: config: created user preferences file: /root/.spamassassin/user_prefs...
Hey @Kaspar , apologize for misleading remark regarding amavis. The host is pure Plesk Obsidian, no 3rd-party tools. Idea of that remark was to ask: perhaps Plesk is controlling what headers to add and where to add them?
I've added pretty basic cf to /etc/spamassassin:
add_header all spam_rules _TESTSSCORES_
`spamassassin --lint` completes without issues.
I've run `sa-update -D` and `systemctl restart spamassassin.service`.
But this header is still missing on incoming messages.
Please advise.
PS: Last time...
Hey @Kaspar , thanks for the quick response!
This might explain some other hickups I've faced with XML API. Will keep in mind that order sometimes matter.
Right now I've worked around this using <update> packet to enable mailbox post email creation.
Hi there!
What are the future plans for a Horde groupware support and what is the best practice around webmail in Plesk?
My concerns are:
- Horde haven't had stable releases in 4 years
- Plesk requires PHP7.4 (outdated) to install Horde
- No mentions of Horde on Plesk' deprecation plan
Thanks!