Eric R. Thern ————–=[ thern dot org ]=————–

7Oct/090

Upgrading MailScanner

Easy Upgrading of MailScanner - RPM version

(For Redhat/Centos - updated from the MailScanner documentation)
1) Make a backup copy of your current MailScanner (Linux):

cp -a /etc/MailScanner /etc/MailScanner.$(date +%Y%m%d)
cp -a /usr/lib/MailScanner /usr/lib/MailScanner.$(date +%Y%m%d)
cp -a /usr/sbin/MailScanner /usr/sbin/MailScanner.$(date +%Y%m%d)

2) Download the latest version and extract

http://mailscanner.info/downloads.html

Check the changelog for upgrade notes and new features:

http://mailscanner.info/ChangeLog

Check the integrity of the downloaded file
untar the archive (tar xzf) X/
cd into the created directory

3) Upgrade MailScanner

run the install script (./install)
inspect the output for errors
manage the .rmpnew files

4) Upgrade the configuration files

upgrade_MailScanner_conf

cd /etc/MailScanner
upgrade_MailScanner_conf MailScanner.conf MailScanner.conf.rpmnew > MailScanner.new
mv -f MailScanner.conf MailScanner.old
mv -f MailScanner.new  MailScanner.conf

upgrade_languages_conf

cd /etc/MailScanner/reports/en
upgrade_languages_conf languages.conf languages.conf.rpmnew > languages.new
mv -f languages.conf languages.old
mv -f languages.new  languages.conf

Don’t forget to upgrade other components periodically as well (SA, DCC, Pyzor, Razor)

5) Restart MailScanner service

service MailScanner restart

6) Check for errors

Check the maillog for errors:

tail -F /var/log/maillog

Run MailScanner with --lint to make sure there are no configuration errors:

MailScanner --lint

Run SpamAssassin with --lint to make sure there are no config errors there either:

spamassassin --lint

- or -

spamassassin --lint -D

(shows output of --lint)

Run check_mailscanner to make sure MailScanner processes are running:

check_mailscanner


7) Send a test mail

If you're really concerned, and want to make sure everything works, it's a good idea to send a couple test mails from external servers to see if they get through your newly updated MailScanner server.

VN:F [1.8.4_1055]
Rating: 0 (from 0 votes)
21Nov/070

Updating Spamassassin on FreeBSD and Plesk

Updating Spamassassin on Plesk and FreeBSD is quite simple without breaking things since the Spamassassin on Plesk is pretty standard.

System: FreeBSD 6.x
Plesk Version: 8.0.x

May work with other versions.

The stock plesk Spamassassin is a 3.1.x variant, which gets pretty old pretty quick. You can upgrade this via the ports by passing a few variables to 'make install' to make sure that you

1) Back up /usr/psa/spamassassin so you have a backup in case something goes wrong:


tar -czf /usr/psa/spamassassin-backup.tar.gz /usr/psa/spamassassin

2) Install the new spamassassin from ports. Please check the prefix, and rules directories to make sure these are good. You can check these by grepping for RULES_DIR on the original plesk /usr/psa/spamassassin/bin/spamassassin file, that will tell you what directories you will want to use.


cd /usr/ports/mail/p5-SpamAssassin

All one line:


make install PREFIX=/usr/local/psa/spamassassin DEF_RULES_DIR=/usr/local/psa/spamassassin/share/spamassassin LOCAL_RULES_DIR=/usr/local/psa/spamassassin/etc/mail/spamassassin

Make sure you run spamassassin --lint to make sure that the rules you have installed are all error free.


/usr/local/psa/spamassassin/bin/spamassassin --lint

Restart spamassassin using:


/usr/local/psa/rc.d/psa-spamassassin restart

It should come back online and work, check the logs to make sure that it has. Send a few emails to make sure your new spamassassin is processing correctly, if so, sit back and enjoy another small plesk victory.

VN:F [1.8.4_1055]
Rating: 0 (from 0 votes)