Prepare a legacy settings archive
The Import legacy settings section of the Settings
page reads either the settings.xml of an earlier MSH application, with its templates directory
next to it, or a tgz archive of the whole etc directory of that application. The archive is the
easier option when the administrator panel does not run on the server where the application is
installed: pack the directory on the server, copy one file to your desktop, and point the import
at it.
Create the archive on the server
Run the command for your application on the server where it is installed. Each command writes the archive into the current directory.
MSH Traffic Policy
tar zcvf msh-tp.tgz -C /opt/msh-traffic-policy/ etc
MSH Disclaimer & Signatures
tar zcvf msh-ds.tgz -C /opt/msh-ds etc
MSH Autoresponder
tar zcvf msh-ar.tgz -C /etc/ msh-autoresponder
If the application was installed in a different location, change the path after -C so that the
last argument names the directory holding settings.xml and, for Traffic Policy and Disclaimer &
Signatures, the templates directory. The import looks for the settings file inside the archive,
so the name of the packed directory does not matter.
Read access to the installation directory is required - run the command as root or with sudo
when the files belong to the application's service user.
Copy the archive to your desktop
Copy the archive to the computer running the administrator panel, for example with scp:
scp user@mailserver:msh-tp.tgz .
Import
- Open the Settings page in the administrator panel.
- In Import legacy settings, click the button of the application the archive belongs to.
- Select the archive. The file chooser accepts both
*.xmland*.tgz. - Read the import report - it lists how many rules and templates arrived and everything that could not be brought across.
The imported rules are added to the rules you already have; nothing is replaced. See Import legacy settings for what is imported and how variables and time ranges are converted.