MailCleaner Virtual Appliance is no more available since March 31, 2025

Looking for a professional and effective alternative? Discover Cleanmail, a smart shield that safeguards your emails from all threats.

Get to know more about Cleanmail

 

 The attached script allows you to switch from version 2016.06 to version 2018.06 of MailCleaner.
The list of changes is accessible at https://new.mailcleaner.net/informations/release.html/

Important notes

  • You may need physical access to your server or a contact with someone with access to the server console. See below, the part about running fsck at reboot.
  • The migration takes approximately one hour.
  • 32-bit servers are no longer supported, only 64-bit versions will be updated.
  • For clusters case, update all servers one by one, the master must be migrated before the slaves.
  • During migration, your MailCleaner server will stop accepting mails. If you use a cluster, the other servers will take care of your traffic. If you use a single server, your mail flow will be held by the sending servers. Those mails will be delivered at the end of the migration.

Procedure

Open all ports needed on your network as described in the installation manual on page 4.

Download this script to your MailCleaner server :
wget --no-check-certificate https://new.mailcleaner.net/downloads/vm/MailCleaner_update.sh
Assign executable permission to the script :
chmod +x MailCleaner_update.sh
[Optional] If you need that our team assist you in case of difficulty, you have to create a screen session by launching :
screen -S MailCleaner
Then start the script itself :
./MailCleaner_update.sh
At the end of the migration, the server will reboot and may run an “fsck” (Check Disk).

Troubleshooting

If the migration script stops and tells you to contact us, follows the instructions to open a ticket. Do not restart the machine.

If the script seems to “run indefinitely,” open a ticket, but don’t interrupt the script.

During the first reboot, the server may take some time to launch all MailCleaner services. This is due to data download for the ClamAV AntiVirus.

Depending on the state of the disk, it may happen that fsck stops and asks to be run manually. In this case, you must know the partition / of your MailCleaner server and restart fsck with the -y option. If your / partition is /dev/sda1 (the most common case), you will need to run:
fsck -y /dev/sda1