Data & backend
Your own business mailbox
Get a real inbox like hello@acme.com in Gmail or Outlook, on the same domain as your Vorx app, without touching your app's email.
Vorx sends email for your app: sign-up confirmations, password resets, receipts. It does not host inboxes. For an address you read and reply from, like hello@acme.com, connect a mailbox provider you choose to the same domain. This page covers Google Workspace and Microsoft 365. Both sit alongside your app and its email, and neither needs any change on the Vorx side.
What Vorx provides
Your app on your domain (see Custom domains), and your app's outgoing email from noreply@notify.acme.com (see Custom emails).
What Vorx does not provide
Mailboxes, a place to read replies, or a mailbox subscription. You buy that from Google or Microsoft, and it stays yours whatever happens to your app.
Why they don't get in each other's way
Every record Vorx asks you to add lives on its own names: @ (an A or ALIAS record) and www for your site, _vorx for verification, and the notify subdomain (send.notify, resend._domainkey.notify, _dmarc.notify) for your app's email. A mailbox provider's records use different names: an MX and an SPF record on your main domain (@), and its own DKIM name. Different names never clash, so you can add a mailbox before or after you connect your app.
Don't point your main domain at Vorx with a CNAME
A CNAME at @ cannot sit beside an MX record, and without an MX your mailbox receives nothing. Use the A record or an ALIAS / ANAME record that the Publish dialog shows, as Custom domains describes.
Before you start
Your domain
The one your app uses, acme.com, and access to its DNS wherever you manage it.
A mailbox subscription
Google Workspace or Microsoft 365, bought from them. Add your domain there first; each will ask you to prove you own it with a TXT record.
Users first
Create your mailboxes (hello@, you@) before you change the MX record, so no mail arrives with nowhere to go.
Google Workspace
In the Google Admin console, add and verify your domain, then add these records. Google's own guides: MX records, SPF, DKIM.
Type
MXName / Host
@Value
smtp.google.comType
TXTName / Host
@Value
v=spf1 include:_spf.google.com ~allDKIM signs your mail. Generate the key in the Admin console under Menu → Apps → Google Workspace → Gmail → Authenticate email (the default selector, google, is the one to use), then add it as a TXT record named google._domainkey with the value Google shows you.
Set up Google Workspace before 2023? Your MX records may start with aspmx. Google still supports them, so if your mail works, leave them.
Microsoft 365
In the Microsoft 365 admin center, open Settings → Domains, add your domain, and follow Manage DNS. If your DNS provider supports Domain Connect, Microsoft can add the records for you. Otherwise add them by hand; the admin center shows the exact values for your domain. Microsoft's guide: Connect your domain by adding DNS records.
Microsoft generates three of its values for your domain, so copy them from the admin center's Add DNS records page, not from here:
- MX at @, priority 0. The value ends in mail.protection.outlook.com.
- CNAME at autodiscover, so Outlook sets itself up (recommended).
- DKIM: two CNAME records, selector1._domainkey and selector2._domainkey (optional, recommended).
Type
TXTName / Host
@Value
v=spf1 include:spf.protection.outlook.com -allSPF and DMARC on your main domain
One SPF record per name
Your main domain (@) may have only one SPF record. If one exists already, add your provider's include: to it rather than creating a second. Don't add Vorx or Resend to it either: your app's email has its own SPF record on send.notify, which you already added.
DMARC for your main domain is a TXT record at _dmarc (not _dmarc.notify, which covers your app's sending subdomain). Start with v=DMARC1; p=none; and tighten it once your mail is flowing. If you turned on show emails as sent from my main domain in Custom emails, keep DMARC's default relaxed alignment. Your app's mail is signed by notify.acme.com, which relaxed alignment accepts for acme.com and strict alignment (adkim=s) does not.
Type
TXTName / Host
_dmarcValue
v=DMARC1; p=none;Questions
No. Your app's records and its sending records use different names from your mailbox's, so your site keeps loading and your app keeps sending from noreply@notify.acme.com.
Not to the default address: noreply@notify.acme.com has no mailbox behind it. If you show emails as sent from your main domain, they come from noreply@acme.com, and a mailbox or alias with that name at your provider receives replies.
No. Buy Google Workspace or Microsoft 365 directly from them. Your mailboxes, billing and data stay with that provider, independent of Vorx.
Yes. The same rules apply: add its MX, SPF and DKIM records exactly as it shows them, keep one SPF record on your main domain, and leave Vorx's records on the notify subdomain as they are.