New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed migration from Dovecot server #3025
Comments
I'm afraid nothing works is too generic. You have to be more specific. I'm just migrating old server and it works. But I've created domains in Mailcow, I've added users through API and I've only migrated e-mails from Cur directories. https://mailcow.docs.apiary.io/#reference/mailboxes/create-mailbox/create-mailbox Q1: You have to update passwords in database adding hash type in the beginning. Like: {PLAIN-MD5}058ef3a0d1812383bdad58552be0eb44 Q2: You don't have to encrypt old e-mails - they are visible without it. |
Using what passwords?
So, how have you actually transferred passwords from the |
Just the same generic password for everyone - it's overwritten later.
I had my passwords in the old mail server database already, but I think it doesn't really matter - you can generate update script from a file. |
Thank you for these tips, I'll try it out. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello,
Hello, I'm trying to migrate from an older cPanel server to the new mailcow-dockerized - but can't make it to work.
I've done the following:
/var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data/
so that the structure is
/var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data/example.com/username
docker-compose exec dovecot-mailcow doveadm quota recalc -A
Nothing works...
Question 1:
How do I actually associate the password data from old server's
/home/username/etc/shadow
?Question 2:
Where do I get private and public
*.pem
keys which are required in the encrypt script ?What am I missing?
Thank you!
The text was updated successfully, but these errors were encountered: