• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

default settings for spamassassin

Z

zeki79

Guest
hi these
anyone know, where i can set the default spamasassin settings?

i have set it unter server/spamasassin, but when i create a new mailbox in a domain, i have other setting...

any idea why?

thanks!

my system:

plesk 7.5.2
suse 9.1
 
Probably because there are two settings. One is server-wide, which is what you set. But when you go to the user's mailbox there are different settings. All you have to do is check the "Server Settings" box and that user's mail will be filtered according to the settings you set in Server>Spamassassin.
 
hi phoenixisp
the box is checked .. thats why i understand it...
 
Not all of the available modules and such are standard fare. Some of them, like Sitebuilder and the Application Vault need to be purchased and a key uploaded to the server to make them functional.
 
i have buy the spamasassin module... (application vault and sitebuilder, too)

what have this to do with spamasassin?
 
Back
Top