Follow the Modoboa install instructions
Follow the roundcubemail install instructions.
Roundcube install is so "one and done" (like Modoboa) in my experience. This article was helpful.
localhost:5432:roundcubemail:roundcube:CHANGEME
localhost:5432:modoboa:modoboa:CHANGEME
localhost:5432:amavis:amavis:CHANGEME
localhost:5432:spamassassin:spamassassin:CHANGEME
- modoboa, amavis:
/srv/modoboa/instance/instance/settings.py
- roundcubemail:
<roundcubemail>/config/config.inc.php
make stop-services
make stop-services
make dump
rsync -azP OLD:modoboa-mail-migration/dumps .
make restore
make drop-dkim-view
See Modoboa upgrade instructions for reference. Since the NEW server is built with latest Modoboa you should just need
sudo -u <modoboa_user> -i bash
source <virtuenv_path>/bin/activate
cd <modoboa_instance_dir>
python manage.py migrate
python manage.py collectstatic
python manage.py check --deploy
exit
make create-dkim-view
Create a domains.make
with a list of domains to sync, e.g.,
DOMAINS := \
domain.com
You can rerun this as needed if mail is still being delivered to OLD server
make sync-mail
sudo bash
scp -r morison.io:dkim/\* /var/lib/dkim
chown opendkim:opendkim /var/lib/dkim/*
make start-services
Likely something will be broken with Modoboa and/or Roundcubemail. Places to look:
/var/log/mail.log
/var/log/nginx/*.log
/var/log/uwsgi/app/*.log
You might need to temporarily change DEBUG = True
in -/srv/modoboa/instance/instance/settings.py
and sudo systemctl restart uwsgi
to get debug messages in the browser. Be sure to revert asap when done.
For debug, it's useful to iron things out with a scratch domain, like mail-test.domain.com
. For the live migration, you'll need to change MX for the domains to the NEW server.