Skip to content

Migration from hardware mailserver

Jump to bottom
Istvan Szabo edited this page Mar 21, 2023 · 5 revisions

You need to edit docker-compose.yml and .env.

docker-compose.yml

You have to change your docker-compose.yml and replace hardware with mailserver2.

For example change:

image: hardware/mailserver:${MAILSERVER_DOCKER_TAG}

to:

image: ghcr.io/mailserver2/mailserver:${MAILSERVER_DOCKER_TAG}

Add new .env variables for the docker tags of postfixadmin and rainloop.

  • image: ghcr.io/mailserver2/postfixadmin:${POSTFIXADMIN_DOCKER_TAG}
  • image: ghcr.io/mailserver2/rainloop:${RAINLOOP_DOCKER_TAG}

Here is an updated docker-compose.sample.yml.

.env

There are three variables you have to adjust:

  • MAILSERVER_DOCKER_TAG
  • POSTFIXADMIN_DOCKER_TAG
  • RAINLOOP_DOCKER_TAG

Take a look at our example .env.

See VERSIONING for more information.

After you migrate you can't go back

The dkim PR was merged.

With this PR the location of the DKIM keys has changed (with automatic migration). They are in the same folder but are now named selector.private.key and selector.public.key. So its not a breaking change, but if someone is automatically using the keys somewhere else, this might need adjustment to the new key names.

So if you go back to hardware/mailserver it would not find your keys and it would create new ones.

Clone this wiki locally