NurtureSite
(435) 465-1595

Leads & CRM

CRM outbound email

Platform or BYO Mailgun, DNS verification, and automation senders.

Configure how automation and nurture emails leave your site. This is separate from lead notification email (alerts when a form is submitted) and from your custom site domain (visitor traffic).

Where to configure

Location What you can do
NurtureSite site page → Outbound email Platform or BYO Mailgun, DNS verification, push to live site
Site admin → CRM → Settings Outbound transport, sender, automation health, BYO Mailgun DNS verify

Outbound email on the NurtureSite site page

CRM settings outbound email and automation health

Changes on the live site sync metadata back to NurtureSite (no API secrets). Factory-pushed defaults apply on first deploy; site overrides are preserved.

Transport options

NurtureSite provisions a subdomain (e.g. your-site.mg.nurturesite.com) under the platform Mailgun account. You add DNS records shown on the site page, then click Verify Mailgun domain.

Bring your own Mailgun

Enter your Mailgun domain and API key in site admin or the NurtureSite portal. Add the SPF/DKIM/MX records Mailgun shows, then verify.

Custom SMTP

Available in site admin → CRM → Settings. Replies go to the configured Reply-To address; inbound reply routing to the CRM is not available on SMTP-only setups.

DNS verification

After saving a Mailgun domain:

  1. Copy each sending and receiving DNS record from the wizard.
  2. Add them at your DNS provider (or Mailgun's DNS if you use their nameservers).
  3. Click Verify Mailgun domain — propagation can take up to an hour.

Your site traffic domain (CNAME to NurtureSite) is unrelated to Mailgun sending DNS. See Custom domains.

Inbound replies

When using platform or Mailgun transport, automation emails use a routable Reply-To on your Mailgun receiving domain. Replies appear in:

  • Site admin → CRM → Leads — reply thread on the lead detail page
  • NurtureSite sales inbox — for prospect/outreach mail on the factory CRM (staff only)

Reply detection in automation conditions works when Mailgun inbound routing is verified.

Automation health

CRM → Settings shows queue and mail status. Automations require:

  • Redis reachable (QUEUE_CONNECTION=redis on the site)
  • Queue worker listening on default and crm queues
  • Scheduler running (ProcessLeadAutomations every 5 minutes)
  • Outbound mail configured and verified

Related articles