• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Mail routing when migrating.

M

migrator

Guest
I have the situation of some 80 domains that I want to migrate and I am in a bit of a confusion on how I will do this without risking losing mail either left on the old machine or lost via permanent bounce.

It would be lovely if I could set the new server to either do "store and forward" to itself or do "soft bounce", so I would set the new DNS MX (which I have with low TTL already) for all the new domains, to the new machine.

And then I could start the migration. As soon as the domains started to be deployed, the store and forward would be converted to a proper delivery to each mailbox.

Could something like this be configured easily, perhaps tweaking Qmail?

Thanks a lot!
 
your best option would be to change the IPs in the dns to point to new server, then migrate. do this late at night/early morning. that way no significant email will be lost.
You may want to block port 25 on the new machine while you do this. In this way the sending servers will get a timeout and should try again as opposed to a "not in my list of rcpthosts" bounce.
 
Back
Top