• 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.

SpamAssasin

C

chuck.boyer

Guest
I'm looking for some general feedback from the community on their experiences with Plesk and SpamAssasin.

- How hard is it to configure?
- Are the definitions updated when the autoupdate process runs?
- Can I configure it on a per mailbox basis?
- If a message is treated as SPAM where does it go? Can the user recover it themselves or does that require an administrator's intervention?
- Can a user create white/black lists?
- Do the white/black lists impact other users on the same server?
- Does Plesk report on the number of mailboxes in a domain where it is configured? For example, if a domain admin adds a mailbox and enables SpamAssasin, do I have visibility as the hoster to bill for that addition?

Thanks.
 
Back
Top