Article ID: 2709, created on Oct 29, 2007, last review on Apr 18, 2012

  • Applies to:
  • Pro Control Panel Linux


View Knowledge
Knowledge ID 1968
Product : Ensim Pro for Linux
Version : 4.0.3
Topic : Hotfix

Hotfix : Spamassassin v 3.0.x Upgrade and issues

Spamassassin v 3.0.x Upgrade (and fix for Maillog errors after spamassassin upgrade)



This KB article enables you to upgrade SpamAssassin to version 3.0.x on Ensim Pro for Linux 4.0.3 servers running any of the following operating systems:

  • Fedora Core 1 (FC1)
  • Fedora Core 2 (FC2)
  • Red Hat Enterprise Linux ES 3 (RHEL 3)
    For information on SpamAssassin, please visit the Web site

Product: Ensim Pro and Basic for Linux
Platform: SSH (Small Scale Hosting) only
Version:4.0.3 (Fedora Core 1, Fedora Core 2 and Red Hat Enterprise Linux                  
Date: April 08, 2005
Patch Description: This is a hotfix for a upgrading to SpamAssassin 3.0.x.
Please note that those running up2date (on RHEL) and yum update (Fedora) should include SpamAssassin package in their skip list.


Download rpms and scripts from and

download appropriate spamassassin rpm designed for your OS from

e.g. for FC1 :

Installation Instructions:

Customers who are upgrading to SA v3.0.x for the first time start from step 1 to 9.

1. Update the SpamAssassin database.

2. Stop the SpamAssassin service.
    service spamassassin stop

3. Download the Ensim Pro for Linux RPMs to a temporary directory,
    for example, /root/spamupgrade_30x

4. Change to the directory created in step 3.
    cd /root/spamupgrade_30x

5. Upgrade the Ensim Pro for Linux RPMs.
   rpm -Uvh *.rpm 
   Note: Do not upgrade the "perl-Net-DNS" rpm if the Ensim Pro for Linux server is running FC2. 

6. Restart the SpamAssassin service.
   service spamassassin restart

7. Run the Ensim Pro for Linux server through the maintenance mode.  

8. Restart the Ensim Pro for Linux server.
   service webppliance restart

9. Synchronize the database with SpamAssassin 3.0.x.

If you have Upgraded SpamAssassin using the above hotfix, you can check with the following Knowledge Base article for further issues:



Related Knowledge

Related Links
Last ModifiedUsageSatisfiedLast Used
6/12/2006 4:20:23 AM463 10/11/2007 2:27:40 AM

4cc899da08664637a8bc437308d3ddd7 3ccb419cf98083f3bb45808fba8dbc7c 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF