• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

SpamAssassin update from 3.3.1 to 3.4.1

webbing

Basic Pleskian
Hi there,

I am just wondering if there is any possibility to update the SpamAssassin package which comes with Plesk 12 from 3.3.1 (obsolete version built in 2010) to the latest one which at the moment is 3.4.1?

Many thanks for your answers or thoughts.
 
In Plesk 12.5 Software requirements:

Anti-spam tools:
  • SpamAssassin 3.x

Vendor of package is OS vendor, not Plesk:

# rpm -qi spamassassin | grep Vendor
Version : 3.3.1 Vendor: CentOS

I suppose that you can upgrade this package from OS or third-party repository.
 
Igor,

The file that handles the updates for spam assassin is: vi /etc/cron.d/sa-update

However in order to configure the version that is compatible with Plesk this automatically wipes the update code in this file and replaces it with # This task was disabled by psa-spamassassin package on a Plesk server. Theoretically I can manually update spamassassin however there would be no guarantee that this would integrate correctly with Plesk and may not be supported by you if this should cause an issue.

Thoughts?
 
The file that handles the updates for spam assassin is: vi /etc/cron.d/sa-update
This file is responsible for Spamassassin filter rules update but not for Spamassassin update.
Plesk works with Spamassassin which was installed on the system. So, if you update it - it should work as expected.
 
I would like to see Plesk give some support to updating some select 3rd party apps that are necessities such as Spamassassin as well. Getting the answer of "you can use a 3rd party repository" to update things that are needed is somewhat frustrating when other posts have a myriad of problems that occur because a 3rd party app has been upgraded outside of what Plesk supports.
 
Last edited:
Ok. My brief instruction for CentOS6.
Note, it is common instruction and you may have own nuances for your system.

1. Install all necessary packages:

# yum install rpm-build openssl-devel gcc make perl-Geo-IP perl-Mail-SPF perl-Net-CIDR-Lite

2. Download src.rpm package from Fedora repository:

# wget ftp://195.220.108.108/linux/fedora-secondary/development/rawhide/source/SRPMS/s/spamassassin-3.4.1-7.fc24.src.rpm

you can take this package from any other repository.

3. Build rpm package:

# rpmbuild --rebuild spamassassin-3.4.1-7.fc24.src.rpm

4. Update spamassassin:

# rpm -Uvh /root/rpmbuild/RPMS/i686/spamassassin-3.4.1-7.el6.i686.rpm

5. Check that it is up and running:

# /etc/init.d/spamassassin status
spamd (pid 21859) is running...
 
First:

+ chmod 755 '/root/rpmbuild/BUILDROOT/spamassassin-3.4.1-7.fc24.x86_64//usr/bin/*'

chmod: cannot access '/root/rpmbuild/BUILDROOT/spamassassin-3.4.1-7.fc24.x86_64//usr/bin/*': No such file or directory

error: Bad exit status from /var/tmp/rpm-tmp.uAURvY (%install)



RPM build errors:

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

Bad exit status from /var/tmp/rpm-tmp.uAURvY (%install)


4. and 5. :No such file or directory.

But I have CentOS7. Reason?

A different setup.

Peace,
Gene
 
Hi Igor,
thank you.

your script stop on last command (update)

Code:
[root@admin home]# rpm -Uvh /root/rpmbuild/RPMS/i686/spamassassin-
3.4.1-7.el6.i686.rpm
error: open of /root/rpmbuild/RPMS/i686/spamassassin-3.4.1-7.el6.i
686.rpm failed: No such file or directory
 
i change the path to:

rpm -Uvh /root/rpmbuild/RPMS/x86_64/spamassassin-3.4.1-7.el6.x86_64.rpm

when i execute this, my ssh tool become in blank page an error that i never seen before
i need to reconnect on sever,

but updated!
thanks
 
I get:

[root@server ~]# rpm -Uvh /root/rpmbuild/RPMS/x86_64/spamassassin-3.4.1-7.el6.x86_64.rpm

error: open of /root/rpmbuild/RPMS/x86_64/spamassassin-3.4.1-7.el6.x86_64.rpm failed: No such file or directory

[root@server ~]#

Peace,
Gene
 
hi, @Gene Steinberg
did you ruining in 32bits?

access this path and see if is correct: /root/rpmbuild/RPMS/
than access full path to see if the files is there.

if all others steps gone ok, the file should be there.
 
Back
Top