• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Updating Spamassassin rules

PGareth

New Pleskian
I am running Plesk 11.5.30 Update #44, Postfix 2.8.14 and Spamassassin 3.3.1 on a Red Hat Enterprise Linux Server 6.5 server. I am looking to update the rules within Spamassassin. I have had a bit of a look and see that a crontab has been created but its a bash script with a comment saying it has been disabled by psa-spamassassin package (/etc/cron.d/sa-update).

Code:
#!/bin/sh

# This task was disabled by psa-spamassassin package
exit 0

Is there a reason why it has been disabled by Plesk? If I update the rules, will it break something?

I have recently added into Postfix RBLs to help toward in reducing the amount of SPAM my customers is getting and this is my next step in a list of things that I would like to change.
 
s there a reason why it has been disabled by Plesk? If I update the rules, will it break something?
The reason is, that Plesk comes with daily/monthly/yearly maintenance scripts, which already include the spamassassin - rules - updates. There is no reason, why the standard - cronjob from the software package should be additionaly executed on the server. ;)

I did look at that documentation and did not help..
Does the above answer, answers YOUR question as well?
 
Back
Top