Plesk 11.x / Linux :: Update The Rules Within Spamassassin?
May 18, 2014
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 reduce 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.
I have a Real Time Web Application Security Rules Subscription. I change the ModSecurity Rule Setup and add the Atomic LoginData to Plesk. All looks fine but the ModSecurity Log is now empty.
- Debian 7 with all Updates - Plesk Version 12.0.18 Update #49
Why isnt Plesk 12 configuring firewalld under CentOS 7 correctly? We have to manuella enable port 8443 and all other ports manually with firewall-cmd..
I have a problem with Parallels Plesk 12 Web Host Edition. In the dashboard, Plesk tells me that Spamassassin service is not running and not installed.
How to setting up it ? Is there a component, a service to buy, or do i have to configure it through SSH ?
Applying Plesk firewall changes? I make my change, apply and get to:
Status: Applying in progress. If your browser shows connection error messages, or if this screen does not disappear in more than 30 seconds, go to previous page.
And there things stay. Going back to look at the firewall I can see the change haven't been applied, and going to apply just results in the same. No error, just no anything. It also took numerous attempts to get firewall modification to be swtich on although finally at about the eighth attempt changes were enabled. Only now I can't apply them ...
I am using the plesk firewall and trying to set up SSH rule which only allows from my IP but deny from everywhere else. In previous versions this worked fine by adding an ip selecting Allow from selected sources, deny from others and the icon in the rules would be orange with the lines
allow incoming from xxx.xxx.xxx.xx Deny incoming from all others
However this no longer works as the deny from all others is not appearing and is not being generated in the iptables by plesk.
I just have installed plesk panel and when i get to the "Firewall" tool, then clicked on "Enable Firewall Rules Management", proftpd has stopped working properly.URLs....I have preinstalled the server 2 times, and every time i try to edit the firewall rules, proftpd got broken.
We are using Plesk 11.5 with postfix MTA. Spamassassin is working fine for incoming mails and leaves outbound mails unchecked - as it should.
Now there is one of my domains whose mails are relayed to another server (using postfix transport tab; mail support for this domain is disabled in plesk). For the moment, these mails arrive without beeing checked and marked by spamassassin. How could I change this? I have tried to register an additional mail-handler like
If there is a direct way to enable spam-control for relay domains, Otherwise I could still access spamassassin via postfix' config-files, but how to use two different implementation of spamassassin at the same time.
What steps can we take to improve SpamAssassin performance? I know this was talked about in older Plesk versions, but we may be able to do more now. What configurations can I do to stop more spam?
I noticed that my spamassassin wasn't running on my server. so I restarted the service from the plesk panel but got the following message:
Error: Unable to make action: Unable to manage service by spammng: spamassassin: unrecognized service ERROR:spammng:Unable to start SpamAssassin service ('--start', 'spamassassin')
So I SSH'ed into my machine and saw that spamassassin wasn't running.
The I reinstalled spamassassin from the "add and remove product components", but that didn't change anything. Still the same error.
Installing Plesk Panel with Spamassassin on Ubuntu 14.04 LTS gives a significant error:
Restarting SpamAssassin Mail Filter Daemon: No /usr/bin/perl found running; none killed. server socket setup failed, retry 1: spamd: could not create IO::Socket::INET6 socket on [::1]:783: Cannot assign requested address server socket setup failed, retry 2: spamd: could not create IO::Socket::INET6 socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 9: spamd: could not create IO::Socket::INET6 socket on [127.0.0.1]:783: Address already in use spamd: could not create IO::Socket::INET6 socket on [127.0.0.1]:783: Address already in use invoke-rc.d: initscript spamassassin, action "restart" failed. dpkg: error processing package sa-compile (--configure):
even though spamassassin (i.e. spamd) is not running. The usual suspects for the before mentioned error, being
a) differences in the name of the PIDFILE variable in /etc/default/spamassassin and /etc/init.d/spamassassin b) directory and/or file location are not readable/writable
are not causing this specific installation bug. The work-arounds:
1 - not installing spamassassin (not an option) 2 - installing spamassassin and (afterwards)
change /etc/default/spamassassin, add the option "-4" to the line OPTIONS, resulting in the line: OPTIONS="--nouser-config -4 --username=popuser --daemonize --helper-home-dir=/var/qmail --virtual-config-dir=/var/qmail/mailnames/%d/%l/.spamassassin --create-prefs --max-children=5" run plesk-installer or autoinstaller again ..Work-around 2 works fine, after reinstallation the /etc/default/spamassassin is as it should be (note that the added "-4" is not present anymore).
The before mentioned work-around suggests some error in the installation process, very likely to be an issue with the chronological order of installation of the various components. In theory, it can be excluded that this bug/issue is caused by psa-spamassassin and/or spamassassin (version 3.3.x) packages, even though some current spamassassin bugs are known: URL....I sincerely hope that Parallels Team can investigate and patch both of the bugs/issues.
I just migrated a bunch of domains from plesk 11.5. Everything appears to be working well however when examining the maillog, I am seeing some strange errors... In this example, the message was delivered and had the spamassassin stuff in the header.
spamd: handle_user unable to find user: 'jason@xxxxxxp.com'
When I set up spamassassin to store spam in the spam folder of my mailbox, it doesn't add any X-Sapm headers nor tags the subject. All I found so far was an old thread where a plesk employee stated that it will be fixed in 'a' future version.
The Plesk panel indicates that the Spam folder can be retrieved using an email client. We are using Outlook 2013 and can not figure out a way to make this happen. We can see the Spam folder using Webmail, but the contents never shows up in Outlook...
I've already stop the spamassassin service on Services Management but it's only valid one day. The next day, spam assassin service automatically start
2. my customer mailbox statistic wrong. Even if their mailbox not full but when they send email. The quota said that their mailbox full. So they can't send/receive email.
Our action : Manually, use command /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f execute-statistics
When I create Mailbox for customer, spamassassin have status (default):
HTML: Status false The score that a message must receive to qualify as spam What to do with spam mail move Add the following text to the true beginning of subject of each message recognized as spam Modify spam mail subject text ***SPAM***
Black list ================================ Server-wide black list:
User's black list:
White list ================================ Server-wide white list:
User's white list:
But i want it:
HTML:
Status false The score that a message must 7 receive to qualify as spam What to do with spam mail text Add the following text to the true beginning of subject of each message recognized as spam Modify spam mail subject text ***SPAM***
Black list ================================ Server-wide black list:
User's black list:
White list ================================ Server-wide white list:
User's white list:
Not Move, it only text at "What to do with spam mail text"
Is it possible through Plesk Linux version on the root servers to update?If not and you will update the Debian itself, you have to note something? What should you back up before everything to make Plesk is working again? Is a complete reinstallation is required?
My current version of nginx in plesk 11.5.44 is 1.5.0 and i would like to update it to the latest stable version which is 1.6.0. However, i cannot seem to manage to do so. I tried with yum update nginx but i receive Package(s) nginx available, but not installed.
After updating from Plesk 10 to Plesk 12 I have lost ssh access for all users (service is not running).
While I select ssh connection I still receive an error:
--------------------------- PuTTY Fatal Error --------------------------- Server unexpectedly closed network connection --------------------------- OK ---------------------------Click to expand...
I want to upgrade to Plesk 12, but want to make sure current version of 11.5.30 is working properly.Whenever Plesk tried to update I get the following error.Installing packages
Loaded plugins: fastestmirror, priorities, refresh-packagekit Loading mirror speeds from cached hostfile * atomic: www5.atomicorp.com * epel: mirror.compevo.com 437 packages excluded due to repository priority protections
[code]....
Fatal error during packages installation: The GPG keys listed for the "CentOS / Red Hat Enterprise Linux 6 - atomicrocketturtle.com" repository are already installed but they are not correct for this package.Check that the correct key URLs are configured for this repository. YumBaseError: The GPG keys listed for the "CentOS / Red Hat Enterprise Linux 6 - atomicrocketturtle.com" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository.
ERROR: Failed to run the Yum utility.The Yum utility failed to install the required packages.
I have VPS Server with Parallels Plesk 11.5.30 (64 bits) on OVH.ORG..Today i do Update to newest version via https://MY-IP:8447
Code: [URL] .....
Now i cant login to my server: [URL] ....
How can i repair it. I dont wanna install again Plesk Panel becouse i have a lot of configuration and email adress.All components like Apache Mysql, ftp works good, but i cant only login.
I've tried a few times to update php on my server from version 5.3 to the latest 5.5 however it keeps conflicting with apache2 that's installed and I ended up having to re-install everything as I accidentally deleted Plesk attempting to fix it.
Ideally I'd rather just run nginx with php-fpm without apache but it's not as straightforward anymore with plesk and how to go about updating PHP?
I've got a clean install of Parallels Plesk v12.0.18_build1200140606.15 running on Ubuntu 12.04.2 LTS.
Symptoms are that two of my domains are not resolved anymore, one of which is my mail, the other the plesk default. So even I try to login by ip, it bounces to the default name and that does not resolve.
This probably happened yesterday morning and i see an autoupdate log, so i can't think what else would cause this out of the blue, since i am on holiday and have not touched the server for three weeks.
The log doesn't really have errors, just one warning i saw, about packages not beeing updated, using old ones. But that was only passenger, so ok i guess. The log is rather big and so i didn't read it all. It ends by saying patch for 12.0.18 will not be applied and errors in apt-get update, that i mentioned.
The domains were set up like many others that still work, as masters.
I can log in as root, so if i could just let me log in by ip again.
Linux auringostaitaan.fi 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64
