TNS Panel
Why were my migrated mailboxes not created?
The panel asks the real DNS where the MX points and skips local mailboxes when mail lives elsewhere, so other tenants' mail is not delivered locally.
If a domain's MX points outside this server (Google Workspace, Microsoft 365 or another provider), the panel deliberately does not create local mailboxes for it.
Why
Adding a mail domain makes this node treat the domain as local. Other tenants' mail to that domain would then be delivered into empty local mailboxes instead of being sent out. Before creating any mail domain the panel asks the real DNS, through a public resolver and not its own DNS, where the domain's mail lives. If the answer cannot be determined it is treated as "not safe".
What the report says
The report states the real MX and how many mailboxes were left out.
Steps
- Confirm the MX of the domain with Migration, Discover.
- If mail should stay at the other provider, do nothing: that is the intended result.
- If you want mail on this node, first move the MX records here, then add the mail domain.
- To copy existing messages over IMAP, use the mailbox import under Email. The destination mailbox must be new and empty.
Last updated: 2026-10-10