When a new version of MailWatch is release upgrading to it is highly suggested: security and bug fixes, and new feature will be present in new releases!
Follow this procedure to make sure that the upgrade process will go as smooth as possible.
- find a good downtime window, this process may take a while when run on big installations
- create a backup of your MailWatch database, safety first!
- read release notes to check if any files change name or path
- stop your mail flow (e.g.: stop yor MTA or block by firewall)
- stop MailScanner
- make a copy of
There are 2 install methods: zip install or git cloning: upgrade procedure differs a bit.
- download the new release zip file
- uncompress it in a temporary directory
- remove old installed directory and replace it with the new one
- replace all cron files with the ones from new release
- cd into MailWatch root directory
Continue upgrade procedure
- eventually adjust
conf.phpwith new configuration entries that
upgrade.phpwarned you about
- symlink, if not already done,
MailScanner_perl_scriptsdirectory to MailScanner custom function directory and copy and edit
MailWatchConf.pmto match the sql settings
- start MailScanner
- restart your mail flow (e.g.: start MTA or unblock by firewall)
- check the mail server logs (e.g.: /var/log/mail.log and /var/log/syslog)
enjoy your upgraded MailWatch!
Several files have changed their name and location in MailWatch 1.2.0, particularly the PHP files that are launched in cron and the Init script files.
Please read the documentation carefully to remove old files during the upgrade.
Upgrading from 1.2.0 to 1.2.1
00MailWatchConf.pm was renamed to
MailWatchConf.pm because it was failing on some perl versions: rename your file accordly and restart MailScanner
$ mv /usr/share/MailScanner/perl/custom/00MailWatchConf.pm /usr/share/MailScanner/perl/custom/MailWatchConf.pm
$ service restart mailscanner