Use XenAI Mail with Google Workspace: keep Gmail, add extra mailboxes
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.
How split delivery works
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.
Before you start
- Add your domain in the XenAI Mail console and prove ownership with the TXT record.
- Choose "Keep my current email provider" under DNS & settings.
- Create the mailboxes you want, for example hari@ and sales@.
Part 1: Add the route
- 1Open the Google Admin console and go to Apps → Google Workspace → Settings for Gmail → Hosts, then click Add route.
- 2Name the route "XenAI Mail". Choose "Single host", enter mail.xenaitech.com and port 25.
- 3Tick "Require mail to be transmitted via a secure (TLS) connection", "Require CA signed certificate" and "Validate certificate hostname".
- 4Click "Test TLS connection", then Save.
Part 2: Add the routing rule
- 1In Settings for Gmail open Routing and click "Add another rule". Name it "XenAI Mail unknown users".
- 2Under "1. Email messages to affect" tick Inbound, "Internal - sending" and "Internal - receiving". Leave Outbound off.
- 3Under "2. For the above types of messages, do the following" choose "Modify message".
- 4In the account types list, UNTICK "Active user accounts" and "Group accounts". Tick ONLY "All inactive and unrecognised accounts".
- 5Under Route, tick "Change route" and choose "XenAI Mail". Tick "Also reroute spam" and "Suppress bounces from this recipient".
- 6Under Spam, choose "Bypass spam filter for this message". Under Encryption, choose "Require secure transport (TLS)".
- 7
DNS for split delivery
- Keep Google's MX records unchanged.
- SPF must include both senders, in a single record:
v=spf1 include:_spf.google.com ip4:<our server IP> ~all. The "Set up automatically" button in the console merges it for you. - Publish exactly one DKIM TXT record for our selector. Two keys for the same selector make Gmail fail DKIM.
- A DMARC record is recommended.
Test it
- From a personal Gmail address to your new XenAI Mail address.
- From a Google user on your domain (for example admin@) to the new address.
- From the new address to a Google user.
- From the new address to someone outside Gmail.
Frequently asked questions
Do I have to leave Google Workspace?
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@.
Will my existing Gmail users be affected?
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.
Why was my test bounced with "Address not found"?
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.
Add XenAI Mail next to Google
Your Gmail users keep working. Add a domain and create your first extra mailbox in minutes.
Set up XenAI Mail