Navigation Menu

Skip to content
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

Closed
vooxo opened this issue Oct 10, 2019 · 5 comments
Closed

Failed migration from Dovecot server #3025

vooxo opened this issue Oct 10, 2019 · 5 comments

Comments

@vooxo
Copy link

vooxo commented Oct 10, 2019

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:

  1. copied emails from the old server; directory structure is as described here: https://www.thecpaneladmin.com/understanding-courier-imap-and-maildir/
  2. put files to:
  3. /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
  4. chown'd everything to 5000:5000
  5. ran docker-compose exec dovecot-mailcow doveadm quota recalc -A
  6. restarted docker

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!

@evilMouse
Copy link
Contributor

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.

@vooxo
Copy link
Author

vooxo commented Oct 11, 2019

I've added users through API

Using what passwords?

Q1: You have to update passwords in database adding hash type in the beginning. Like: {PLAIN-MD5}058ef3a0d1812383bdad58552be0eb44

So, how have you actually transferred passwords from the /home/username/etc/shadow file to the new server and associated them with users?

@evilMouse
Copy link
Contributor

I've added users through API

Using what passwords?

Just the same generic password for everyone - it's overwritten later.

Q1: You have to update passwords in database adding hash type in the beginning. Like: {PLAIN-MD5}058ef3a0d1812383bdad58552be0eb44

So, how have you actually transferred passwords from the /home/username/etc/shadow file to the new server and associated them with users?

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.

@vooxo
Copy link
Author

vooxo commented Oct 25, 2019

Thank you for these tips, I'll try it out.

@vooxo vooxo closed this as completed Oct 25, 2019
@vooxo vooxo reopened this Oct 25, 2019
@stale
Copy link

stale bot commented Dec 24, 2019

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.

@stale stale bot added the dunno label Dec 24, 2019
@stale stale bot closed this as completed Dec 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants