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

spamassassin

A

awdau

Guest
Howdy,

How do I disable spam assassin within qmail on the plesk server, but leaving all the option available within plesk?

Cheres
cya
Andrew
 
Hello,

Not sure exactly what you need, but you can disable spamassassin from Server -> Spamassassin.
 
We want all the plesk options available via the web interface, but not actually use the spamassassin that comes with plesk. Surely there has to be a way of disabling it within qmail.
 
sorry i do not understand that, what do you like to do with the options when there is no spamassassin ?
 
We want the interface, but we have our own implementation of spam filtering.

This includes stopping the **** before it even gets in the first place, so that spamassassin doesn't even see it and wasting **** loads of resources. (about 80% of the **** that hits our current system is rejected during MAIL/RCPT time.)

We want the spam assassin interface features available to use with our system, but remove all the plesk spamassassin stuff, so it doesn't do a second scan and adding the extra headers, etc
 
Back
Top