MX conflicts
Keep an existing inbox working while using Reloop — when MX changes are safe and when to use a separate hostname.
MX records decide where inbound mail is delivered.
Sending-only with an existing inbox
If you only need Reloop to send, keep your current MX where it is. Publish SPF, DKIM, DMARC (and tracking) for Reloop without replacing MX.
Receiving with Reloop
Enabling Reloop receiving sets MX toward inbound.reloop.sh. On the same hostname, that typically stops delivery to any other inbox on that name.
Safe pattern
Use separate hostnames:
acme.comMX → your existing inboxmail.acme.comMX → Reloop (inbound + Reloop send)
Reloop supports the root, a subdomain, or both. See also Sending vs receiving.
Multiple MX priorities
If you experiment with multiple MX targets, lower priority number = higher preference. Mixing two inbox providers on one hostname is advanced and usually the wrong fix — prefer a separate hostname for Reloop receiving.
Was this page helpful?
- Need help? Contact Support.
- Chat with Reloop developers on Discord.
- Check out our changelog.
- Questions? Contact Sales.
- LLM? Read llms.txt.