Multi server
This page removes MSH Zimbra Rules from a multi-server installation. On a single server, see Single server.
Remove it in this order:
- The zimlets and the extension, from the mailbox servers.
- Every MTA server.
- The web admin server, last.
To take only one MTA server out and keep the others, run Every MTA server on that server only, then remove it on the Servers page of the web admin.
The zimlets and the extension, on the mailbox servers
Skip this if you did not install them with Zimlets configuration.
Commands
On one mailbox server:
sudo su - zimbra -c 'zmzimletctl undeploy com_mshsoftware_change_user_info'
sudo su - zimbra -c 'zmzimletctl undeploy mshsoftware-zimlet-change-user-info'
On every mailbox server:
sudo rm -rf /opt/zimbra/lib/ext/msh-zr /opt/zimbra/conf/msh-zr-extension.properties
sudo su - zimbra -c 'zmmailboxdctl restart'
Description
Run the zmzimletctl commands on one mailbox server. They run as the zimbra user, so each one switches to it with sudo su - zimbra -c.
Undeploy Change User Info for the Classic web client. Zimbra removes it from all mailbox servers:
sudo su - zimbra -c 'zmzimletctl undeploy com_mshsoftware_change_user_info'
Undeploy Change User Info for the Modern web client:
sudo su - zimbra -c 'zmzimletctl undeploy mshsoftware-zimlet-change-user-info'
Remove the extension and its configuration, on every mailbox server:
sudo rm -rf /opt/zimbra/lib/ext/msh-zr /opt/zimbra/conf/msh-zr-extension.properties
Restart mailboxd as the zimbra user, on every mailbox server, so it unloads the extension:
sudo su - zimbra -c 'zmmailboxdctl restart'
If you opened the web admin port 7081 to the mailbox servers, close it again on the web admin server.
Every MTA server
Repeat this section on each MTA server.
Commands
sudo su - zimbra -c 'zmprov ms $(zmhostname) zimbraMtaSmtpdMilters ""'
sudo su - zimbra -c 'zmprov ms $(zmhostname) zimbraMtaNonSmtpdMilters ""'
sudo su - zimbra -c 'zmprov ms $(zmhostname) zimbraMtaMilterDefaultAction ""'
sudo su - zimbra -c 'zmmtactl reload'
sudo systemctl stop msh-zr-milter.service msh-zr-node.service
sudo systemctl disable msh-zr-milter.service msh-zr-node.service
sudo rm -rf /opt/msh-zr
sudo systemctl daemon-reload
sudo userdel msh
Description
The zm... commands run as the zimbra user, so each one switches to it with sudo su - zimbra -c.
Clear the milter attributes that were set when you registered the milter, so Zimbra stops routing mail through the milter. Setting an attribute to an empty value with zmprov ms removes it from the server entry, so Zimbra falls back to its default for that setting.
sudo su - zimbra -c 'zmprov ms $(zmhostname) zimbraMtaSmtpdMilters ""'
sudo su - zimbra -c 'zmprov ms $(zmhostname) zimbraMtaNonSmtpdMilters ""'
sudo su - zimbra -c 'zmprov ms $(zmhostname) zimbraMtaMilterDefaultAction ""'
If zimbraMtaSmtpdMilters also contains Zimbra's own milter (e.g. inet:localhost:7026, see the caveats), do not clear the attribute. Instead, set it again with only the MSH entry removed:
sudo su - zimbra -c 'zmprov ms $(zmhostname) zimbraMtaSmtpdMilters "inet:localhost:7026"'
Check the current value first with zmprov gs $(zmhostname) zimbraMtaSmtpdMilters.
Zimbra's built-in milter server (zimbraMilterServerEnabled) was enabled during installation only as a workaround for Zimbra Bug 97706. Leave it enabled if you use it for distribution-list access control; otherwise you can switch it off again:
sudo su - zimbra -c 'zmprov ms $(zmhostname) zimbraMilterServerEnabled FALSE'
sudo su - zimbra -c 'zmmilterctl stop'
Reload the Zimbra MTA, so Postfix regenerates main.cf without the milter:
sudo su - zimbra -c 'zmmtactl reload'
To verify, run postconf smtpd_milters non_smtpd_milters milter_default_action: inet:localhost:7080 must no longer appear in the output.
Stop the node and the milter:
sudo systemctl stop msh-zr-milter.service msh-zr-node.service
Prevent them from starting on boot. This also removes the links to the unit files created during the installation:
sudo systemctl disable msh-zr-milter.service msh-zr-node.service
Delete all application files, including the node's local copy of the rules:
sudo rm -rf /opt/msh-zr
Reload systemd, so it forgets the removed services:
sudo systemctl daemon-reload
Remove the msh service user:
sudo userdel msh
The web admin server
Remove the web admin last, once no MTA server uses it any more.
/opt/msh-zr/etc/msh-zr-master.db holds all your rules and settings and /opt/msh-zr/etc/msh-zr-web.db the servers, web admin users and directory service settings. Both are deleted with the installation. Export a backup on the Backup & Restore page, or copy /opt/msh-zr/etc, first if you may want to restore the installation later.
Commands
sudo systemctl stop msh-zr-web.service
sudo systemctl disable msh-zr-web.service
sudo rm -rf /opt/msh-zr
sudo systemctl daemon-reload
sudo userdel msh
Description
The web admin server has no Zimbra MTA, so there is no milter to detach.
Stop the web admin:
sudo systemctl stop msh-zr-web.service
Prevent it from starting on boot. This also removes the link to the unit file created during the installation:
sudo systemctl disable msh-zr-web.service
Delete all application files, including the configuration and the databases (see the note above):
sudo rm -rf /opt/msh-zr
Reload systemd, so it forgets the removed service:
sudo systemctl daemon-reload
Remove the msh service user:
sudo userdel msh
If you opened ports 7081 or 7082 in a firewall for MSH Zimbra Rules, close them again.