Topic: Domain Staging (i.e. advance creation of users and groups)
==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.3.1
- Deployed with iRedMail Easy or the downloadable installer? Installer
- Linux/BSD distribution name and version: CentOS 8 Basic
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MariaDB
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
This question is about moving domains over to an iRedMail server in a slow and methodical way.
Imagine I have five domains, a.com, b.com ... e.com, all handled on another email server product. I don't want to switch them all at the same time (too many support calls). So I move them one at a time.
- In iRedMail, set up a.com (slowly and carefully adding users, synonyms, lists, etc).
- move all the mail over using (e.g.) imapsync
- change the MX records for a.com
- tell the old server that a.com is not handled locally
- done (more or less)!
Step 2. I'm stuck!
I can't set up b.com slowly, because as soon as I create it, any email created from firstname.lastname@example.org to email@example.com is treated as a local message, and thus will fail until firstname.lastname@example.org is created. Also, I'd have to telll user2 to check both email servers for messages during the transition period.
Thus my question:
Is there a way to populate a complete domain in iRedMail, while still having other domains on the same server treat it as external? That is, a.com emails need to look at b.com's MX record and see that the old server is still handling b.com email.
Does the "Enable this Domain" checkbox in the Admin Panel do this? Or does it just turn off message handling for the domain?