Skip to main content
WisMail

Upgrade your mail server

An upgrade installs the newer .deb package over the old one. Your configuration (mailserver.cfg, users.cfg), certificates, settings, license and the message store are not part of the package, so they stay untouched. Allow 15 minutes and a short window in which mail services restart.

1. Check the subscription rule first

Every release has a build date. Your license key carries a subscription expiry date, and the server will not run a build released after that date. So:

  • You can keep running the installed build after the subscription expires (as long as the license itself is valid), but you cannot move to a release dated after the expiry.
  • If you try, the upgrade is refused before anything is changed: the installed version stays and keeps running, and the message tells you how to renew and download an eligible version.
  • To upgrade to a newer release, renew the subscription, install the new key (license activation), then install the package. Prices and renewals: Pricing.

2. Back up first

  1. In web administration open Configuration, Archiving and Backup and run a Copy backup with Start now (see the backup guide), then copy the zip files off the server.
  2. Read the release notes on the Download page.

3. Upgrade

Download the new package from the Download page, verify its SHA-256 as in the install guide, then:

sudo apt install ./wismail_<version>_amd64.deb

The installer stops the service, replaces the program files and starts it again. Mail services are unavailable for a short time while it restarts; senders retry delivery, so incoming mail is queued by other servers rather than lost.

4. Check health after the upgrade

systemctl status wismail
sudo journalctl -u wismail -e

The status must show active (running). Then:

  1. Log in to web administration (https://<host-name>:4040/admin) and check the dashboard and the version and build number.
  2. Look at the Error and Warning logs for new messages.
  3. Send and receive a test message, log in to webmail and sync one mobile device.

The server can also check an update server and tell you that a newer release exists; installing is always your decision.

5. If something goes wrong

Stop the service, reinstall the previous package version and compare against your backup. Rehearse the upgrade and the way back on a test server before you do it on the production server. If a problem remains, keep the logs and contact us.

Next steps