Loading…
You do not have to move your team. Google stays your MX and your Gmail users stay put. Addresses Google does not know, like hari@ or sales@, are routed to real XenAI Mail mailboxes on the same domain. It works in every direction: Gmail to XenAI Mail, XenAI Mail to Gmail, and to the outside world.
Google receives every message first. If the address belongs to a Google user, it stays in Gmail. If not, one routing rule hands it to mail.xenaitech.com.
v=spf1 include:_spf.google.com ip4:<our server IP> ~all. The "Set up automatically" button in the console merges it for you.No. In split delivery your domain keeps Google as its MX, and your Google users stay exactly where they are. XenAI Mail only serves the extra addresses you create here, such as hari@ or sales@.
Not if the routing rule is set to "All inactive and unrecognised accounts" only. Google keeps delivering to every address it knows. Only addresses Google does not recognise are handed to XenAI Mail. Never tick "Active user accounts" or "Group accounts" on that rule.
Usually the rule does not include "Internal - sending", so mail from your own Google users to the new address never reaches the route. Add it, wait a few minutes (up to an hour) and test again. Also check that the mailbox exists in XenAI Mail and that the route host is mail.xenaitech.com on port 25.
Each XenAI Mail mailbox costs credits per month, starting at 20 credits for 500 MB. Google Workspace billing is unchanged. Aliases and groups are free.
The idea is the same: keep your current provider as MX and route unknown recipients to mail.xenaitech.com with a Microsoft 365 mail-flow rule. Step-by-step instructions for Microsoft 365 are coming soon.
Yes. Create every mailbox you need in XenAI Mail, switch the domain to "Move all of this domain's mail to XenAI Mail" in the console, then point MX to XenAI Mail as the last step.
Your Gmail users keep working. Add a domain and create your first extra mailbox in minutes.
Set up XenAI Mail