What is an MX Record?
MX (Mail Exchanger) records specify where incoming mail should be delivered for a domain. Every MX record has a priority value—the lower the number, the higher the priority. Migma requires you to set up an MX record onsend.[sending-domain] to establish a return-path for bounce and complaint reports from inbox providers. If your sending domain is mail.yourdomain.com, the MAIL FROM hostname is send.mail.yourdomain.com.
Won’t This Conflict with My Existing Email Provider?
No, it won’t. Here’s why:How MX Records Work
MX records only affect the specific subdomain (or domain) they’re associated with. They don’t impact other subdomains or the root domain.Example: You Use Google Workspace
Say you’re using Google Workspace for your email. You’ll have MX records that look like this:anything@yourdomain.com should be delivered to Google’s servers.
Adding Migma’s MX Record
When you add a sending domain to Migma, you need to add an MX record forsend.[sending-domain]:
- The Migma MX record is for the
sendhostname under your sending domain - Your Google MX records are for your inbox domain
- These are separate hostnames
Your existing email flow is unaffected.
Why Migma Uses the send Subdomain
Migma specifically uses the send subdomain for the MAIL FROM (return-path) because:
- No conflicts - It doesn’t interfere with your existing MX records
- Better deliverability - Bounce handling is properly configured
- Separation of concerns - Sending infrastructure is isolated from receiving
Common MX Record Conflicts
Existing record on `send` subdomain
Existing record on `send` subdomain
Problem: You already have an MX record for
send.[sending-domain] from another service.Solutions:- Remove the existing record if you no longer use that service
- Use a different subdomain in Migma (contact support for custom MAIL FROM subdomain configuration)
Same priority value (10) already in use
Same priority value (10) already in use
Problem: You have another MX record with priority 10 for the same subdomain.Solution: Each MX record should have a unique priority. Either:
- Change Migma’s priority to a different number (e.g., 5)
- Update your existing record to a different priority
If two MX records have the same priority, mail servers will randomly choose one per delivery attempt—they won’t deliver to both.
DNS provider auto-appending domain name
DNS provider auto-appending domain name
Problem: Your MX record appears as:Instead of:Solution: Add a trailing period (dot) at the end of the MX value:The trailing period tells your DNS provider this is a fully qualified domain name that should not be modified.
Checking Your MX Records
Using a Web Tool
Use MXToolbox or DNS Checker to verify your MX records:- Enter
send.[sending-domain], such assend.mail.yourdomain.com - Select “MX Lookup”
- Verify the record matches what Migma provided
Using the Terminal
Summary
The only conflict occurs when you already have something on the exact same full MAIL FROM hostname, such as
send.mail.yourdomain.com.
Next Steps
Domain Verification Issues
Troubleshoot verification problems
Add Sending Domain
Complete domain setup guide