GoHighLevel Email Deliverability: Mailgun Setup (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 24 July 2026 · 10 min read

On this page: Why deliverability tanks in GHL · LC Email vs your own Mailgun account · Dedicated sending domain setup (SPF, DKIM, DMARC) · The 4-week warm-up schedule · List hygiene and engagement segmentation · Monitoring and the Gmail/Yahoo bulk-sender rules · Common mistakes to avoid · FAQ

GoHighLevel email deliverability is the difference between a campaign that books appointments and one that quietly dies in spam folders. I audit GHL sub-accounts every week in Australia and the pattern is consistent: solid offer, decent copy, open rates under 10% because the sending infrastructure was never set up.

The good news: deliverability is not a dark art, it is a checklist — a dedicated sending domain, three DNS records, a disciplined warm-up, a clean list and a couple of dashboards checked weekly. This guide walks through the full Mailgun and LC Email setup for 2026, including the Gmail and Yahoo bulk-sender requirements that now make or break HighLevel email deliverability at volume.

Why email deliverability tanks in GoHighLevel

GHL itself is not the problem — it hands you Mailgun-grade infrastructure that most agencies never configure. Three failure modes account for almost every poor-deliverability sub-account I see.

Sending from a shared domain

Fresh sub-accounts that never add a dedicated sending domain send through shared LeadConnector infrastructure, so your reputation is pooled with every other unconfigured account on that range — including the ones blasting cold outreach. When their complaints spike, your inbox placement suffers.

No dedicated sending domain, no authentication

If SPF, DKIM and DMARC are missing or misaligned, Gmail and Yahoo now treat your mail as unauthenticated bulk. Since the 2024 sender requirements tightened (and they have only been enforced harder since), unauthenticated bulk mail is rejected or junked outright. There is no charm offensive that gets around missing DNS records.

Cold lists and purchased data

Importing a purchased list into a sub-account and hitting send is the fastest way to destroy a domain: cold lists are riddled with spam traps, dead mailboxes and people who never consented. In Australia this is also a legal problem: the Spam Act 2003 requires express or inferred consent, a functional unsubscribe, and accurate sender identification for commercial electronic messages, and ACMA has issued seven-figure penalties for breaches. Deliverability and compliance fail together.

LC Email vs your own Mailgun account: which to use

GoHighLevel gives you two sending options, and the right choice depends on how your agency operates.

When LC Email makes sense

LeadConnector Email (LC Email) is the native default: billing runs through your GHL wallet, dedicated sending domains are configured inside the sub-account with a guided DNS wizard, and there is no separate Mailgun account to maintain. For agencies running client sub-accounts at typical volumes — nurture sequences, appointment reminders, newsletters — LC Email is the sensible choice in 2026.

When your own Mailgun account makes sense

Connecting your own Mailgun account (via the agency-level SMTP/Mailgun integration) suits three situations: high volumes where you want Mailgun’s raw logs, suppression management and dedicated IP options; existing Mailgun infrastructure and pricing; or granular control over sending domains and routing per client. The trade-off: you own the maintenance — API keys, verification and billing sit outside GHL.

Either way, the non-negotiable holds: every sub-account that sends marketing email needs its own dedicated sending domain, one per client, so no client’s bad habits poison another’s reputation. If you are weighing GHL against a standalone email platform, my GoHighLevel vs Mailchimp comparison covers where the sending infrastructure differs.

Step-by-step: dedicated sending domain with SPF, DKIM and DMARC

Here is the exact sequence I run for every new sub-account. Allow 30 minutes plus DNS propagation.

1. Choose a subdomain, not your root domain

Send from a subdomain such as mail.yourclient.com.au or em.yourclient.com.au. This isolates email reputation from the website domain and gives you room to segment later.

2. Add the dedicated domain in GHL

In the sub-account, go to Settings → Email Services → Dedicated Domain and IP → Add Domain (for LC Email), or add the domain inside Mailgun and connect it via Settings → Email Services → SMTP Service if you run your own Mailgun account. GHL generates the DNS records you need; the official steps are documented in the GoHighLevel help centre.

3. Publish the DNS records

At your DNS host (Cloudflare, Crazy Domains, VentraIP — wherever the zone lives), add the records GHL or Mailgun provides:

• SPF — a TXT record on the sending subdomain, typically v=spf1 include:mailgun.org ~all. One SPF record per host name only; merge includes if a record already exists.
• DKIM — a TXT record (for example krs._domainkey.mail.yourclient.com.au) containing the public key. This is what cryptographically signs each message.
• DMARC — a TXT record at _dmarc.yourclient.com.au. Start with v=DMARC1; p=none; rua=mailto:[email protected] so you collect reports without blocking anything, then move to p=quarantine once reports show clean alignment.
• Tracking CNAME and MX — add the CNAME for open/click tracking and the MX records if Mailgun will receive replies on the subdomain.

4. Verify and send a live test

Back in GHL or Mailgun, click verify once DNS has propagated (minutes on Cloudflare, up to 24 hours elsewhere). Then send a test to a Gmail address and use “Show original” to confirm three green results: SPF: PASS, DKIM: PASS, DMARC: PASS. Do not send a campaign until all three pass and the From address uses the authenticated domain, so DMARC alignment holds.

The 4-week domain warm-up schedule

A brand-new domain has zero reputation, and mailbox providers distrust sudden volume from an unknown sender. Warm-up means starting small with your most engaged contacts and roughly doubling volume as metrics stay clean. Here is the schedule I use for a list of around 10,000 contacts; scale proportionally.

If any metric slips — a bounce spike, a complaint above 0.3%, sudden spam placement — hold or halve volume for a few days. In GHL, use Workflows with wait steps and drip-mode sending to throttle volume automatically.

List hygiene and engagement segmentation

Authentication gets you assessed fairly; engagement earns inbox placement. Mailbox providers watch how recipients treat your mail, so who you send to matters more than what you send.

Clean before you send

Run new or aged lists through a verification service before they touch your dedicated domain, and delete role addresses (info@, admin@), obvious typos and anything that hard-bounces. Inside GHL, keep smart lists for hard bounces and unsubscribes and exclude them from every Workflow. Confirm every contact has a consent source recorded — under the Spam Act 2003 you must be able to show express or inferred consent, and opt-outs must be actioned within five business days (GHL’s native unsubscribe link handles this, so never strip it from email templates).

Segment by engagement, sunset the dead weight

Tag contacts into engagement tiers — 30-day, 90-day, 180-day — using Workflow triggers on opens and clicks, and weight your sending heavily toward the top tiers. Contacts silent beyond 180 days get a short three-email re-engagement sequence; non-responders get suppressed. It feels brutal to cut a third of the list, but 5,000 contacts at a 35% open rate outperform 15,000 at 8% — and protect your reputation for every send that follows. If you are tracking this properly, tie it back to revenue with the approach in my guide to measuring GoHighLevel ROI with key KPIs.

Watch your copy too: all-caps subject lines, excessive punctuation and spam trigger words (“free money”, “act now”) still add friction with content filters, especially on a young domain.

Monitoring, thresholds and the Gmail/Yahoo bulk-sender rules

The numbers to hold

Check these weekly in your GHL email statistics or Mailgun dashboard: bounce rate under 2% (investigate at 2%, stop and clean at 4%), spam complaint rate under 0.1% with 0.3% as the absolute red line, and unsubscribe rate under 0.5% per send. A rising bounce trend almost always means list decay; a complaint spike means you emailed people who never expected to hear from you.

Google Postmaster Tools

Register your sending domain at Google Postmaster Tools the day you verify it. It is free and shows your domain and IP reputation, user-reported spam rate, and SPF/DKIM/DMARC success rates as Gmail actually sees them — the only view that matters, since Gmail dominates most Australian lists.

Gmail and Yahoo bulk-sender requirements in 2026

Send 5,000+ messages a day to Gmail addresses and you are a bulk sender who must meet all of the following, or your mail gets rejected: SPF and DKIM authentication with a published DMARC policy and an aligned From domain; one-click unsubscribe (RFC 8058 List-Unsubscribe headers, added automatically by GHL and Mailgun) honoured within two days; and a user-reported spam rate under 0.3% in Postmaster Tools — ideally under 0.1%. Yahoo enforces an equivalent set. These are entry requirements now, not best practices — and the same gatekeeping applies to SMS via carrier registration, covered in my GoHighLevel A2P 10DLC registration guide.

Common mistakes to avoid

• Sending from shared LeadConnector infrastructure indefinitely — the dedicated sending domain is step one, not a later optimisation.
• Blasting the full list on a brand-new domain — skipping warm-up torches reputation in days and takes months to rebuild.
• Publishing two SPF records on the same host name — multiple SPF records make validation fail entirely; merge the includes into one record.
• Setting DMARC to p=reject on day one — start at p=none, read the reports, fix alignment, then tighten the policy.
• Using one sending domain across multiple client sub-accounts — one bad client campaign then drags every client’s deliverability down.
• Ignoring bounce and complaint dashboards until a campaign fails — by the time inboxing visibly collapses, the reputation damage is weeks old.

If you want your sending domain, DNS records and warm-up handled properly the first time, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

Should I use LC Email or my own Mailgun account in GoHighLevel?

Use LC Email unless you have a specific reason not to. It is native, supports dedicated sending domains per sub-account, and needs no external maintenance. Connect your own Mailgun account only if you need high-volume features like dedicated IPs, raw log access or existing negotiated Mailgun pricing.

How long does it take to warm up a new sending domain?

Plan on four weeks for most lists: start at 50–100 emails per day to your most engaged contacts and roughly double weekly while bounce stays under 2% and complaints under 0.1%. Larger lists or any metric wobble can stretch this to six or eight weeks — pushing faster usually costs more time than it saves.

What SPF, DKIM and DMARC records does GoHighLevel need?

Three TXT records on your sending subdomain: an SPF record (typically v=spf1 include:mailgun.org ~all), the DKIM public key GHL or Mailgun generates for the _domainkey host, and a DMARC record at _dmarc starting with p=none plus a reporting address. GHL displays the exact values when you add the dedicated domain, and verification confirms they resolve.

Why are my GoHighLevel emails going to spam even with SPF and DKIM passing?

Authentication is a prerequisite, not a guarantee. The usual culprits are a cold or unwarmed domain, poor engagement from an aged list, a complaint rate creeping past 0.1%, misaligned From domains breaking DMARC, or spammy copy. Check Google Postmaster Tools for your actual domain reputation and spam rate, then fix the worst metric first.

Do the Gmail bulk-sender rules apply to my Australian business?

Yes — the rules apply based on where your recipients’ mailboxes are, not where you are. If you send 5,000+ daily messages to Gmail accounts you must have SPF, DKIM, an aligned DMARC policy, one-click unsubscribe and a spam rate under 0.3%. On top of that, the Spam Act 2003 requires consent, sender identification and working unsubscribe for all commercial email sent to Australian addresses, regardless of volume.