Sending vs receiving

Reloop can send mail as your domain, receive mail into Reloop, or both. DNS requirements differ.

New domains start with Email Sending, Email Receiving, and click/open tracking on. Turn Receiving off before publishing DNS if this hostname must keep another inbox (Google Workspace, Microsoft 365, etc.).

Sending (outbound)

Goal: Gmail/Outlook/others accept mail from you@yourdomain.com as authenticated.

Typically involves:

• SPF — authorize Reloop (include:reloop.sh)
• DKIM — sign messages (reloop._domainkey)
• DMARC — policy for failures (required for Reloop verification when Email Sending is on)
• Tracking CNAME — on by default for new domains (link on apex, or link.<subdomain> when using a subdomain) → link.reloop.sh

Sending does not require an MX record. MX is only for inbound mail.

You can keep another provider as the inbox on the same domain if you leave Email Receiving off and do not publish Reloop’s inbound MX for that hostname.

Receiving (inbound)

Goal: Mail addressed to your domain is delivered into Reloop (Agent Inbox / inbound pipelines).

Requires Receiving MX pointing at Reloop’s inbound host, typically:

inbound.reloop.sh

(with the priority shown in the dashboard).

Dashboard toggles

On the domain DNS Records and Configuration tabs you can enable or disable sending, receiving, and tracking. When you change them, Reloop shows which DNS rows are required. Publish what the dashboard marks as needed, then verify again.

Practical recipes

Related

• DNS records explained
• MX conflicts