Chatmail: SMTP-Data-Error after migration (541)

Mutual Help
1

Hi,

I migrated my installation to another server and followed the instructions from the guide:

I saw the expected behavior during the transfer:
The Client (android) could not connect after I shut down chatmail on the old server.
Everything built great on the new server.
After importing vmail and running cmdeploy run, the client could connect.

So it seems the users could be transferred successfully.

I created a new testaccount via the qr-code from my server’s website, this also went great, but I was unable to send/receive mails between the existing and the new account from my server.

I have an existing account on another server and I can send from this to the old account from my server (but not the other way around) because they are already connected.
This account is unable to send to the new account on my server because guaranteed e2e-encryption can’t be established.

For Both accounts from my server, I get the following error message when I try to send an email:

Send error: permanent: Error: (SMTPDataError) (451, b’4.7.1 Service unavailable - try again later’)

I deleted all DNS-records and recreated them according to the output of cmdeploy run and cmdeplay dns.
I ran the chown commands according to the guide again and I restarted my VPS.
Because I’m new to the software related to mail servers I’m totally lost here at the moment.

2

I found the solution: The dkimkeys could not be accessed (according to journalctl -u opendkim) because owner was the rood-user.
The reason for this is the command chown root: -R /etc/dkimkeys in the migration guide.
This should be chown opendkim: -R /etc/dkimkeys to make the opendkim user/group the owner.

I also opened an issue on the github-page with solution.