Upgrade from from Mailserver 1.1.3 or lower to to Mailserver 1.2.x - t-lo/mailserver GitHub Wiki
Some start-up / service unit enhancements were introduced in 1.2.0. This is a breaking change; upgrading required manual porting of existing customisations. If you're upgrading please read on.
Core mailserver
Mailserver service start-up script wrapper (start_mailserver.sh) has been moved to systemd/. Customisations to start-up in ./start_mailserver.sh must be ported to systemd/start_mailserver.sh.
Consequently, the service file in systemd/mailserver.service has been updated with the new path of the start-up wrapper script.
- Either, the new service file must be copied from
systemd/mailserver.serviceto/etc/systemd/system/(and customisations in the existing/etc/systemd/system/mailserver.service- like e.g. custom HTTP / HTTPS ports - must be ported to the new unit file). - Or, the existing
/etc/systemd/system/mailserver.servicemust be updated to point to the new start-up script.
Monitoring
Mailserver 1.2.0 ships monitoring services (grafana, promentheus, and pughgateway) as separate systemd services instead of spawning background jobs from a single start-up script.
If monitoring is enabled, all respective mailserver-monitoring* service files in systemd/ must be installed and enabled. Existing customisations in start_monitoring.sh must be ported to the respective service startup wrapper in systemd/mailserver-monitoring*.sh.
# Check script wrappers systemd/mailserver-monitoring*.sh and port customisations from start_monitoring.sh; then
systemctl stop mailserver-monitoring
cp systemd/mailserver-monitoring*.service /etc/systemd/system/
systemctl daemon-reload
systemctl enable mailserver-monitoring-grafana.service mailserver-monitoring-network.service mailserver-monitoring-prometheus.service mailserver-monitoring-pushgw.service mailserver-monitoring.service
systemctl start mailserver-monitoring