GoHighLevel SMTP Setup: The Complete Guide (2026)

Why Custom SMTP Matters in GoHighLevel

GoHighLevel's built-in LC Email service is powered by Mailgun on shared infrastructure. For low-volume agencies and basic automations, it works. For anything serious — client campaigns, high-volume sequences, or any situation where inbox placement directly affects revenue — you need custom SMTP.

Custom SMTP gives you:

• Your own sending reputation (not shared with thousands of GHL accounts)
• Your own dedicated domain and IP (controllable and monitorable)
• Better deliverability (because you control the infrastructure)
• Provider choice (Mailgun, SendGrid, AWS SES, self-hosted)

The trade-off: you lose detailed delivery stats inside GHL. We'll cover how to handle that.

Step 1: Choose Your SMTP Provider

Provider	Best For	Starting Price	GHL Compatibility
Mailgun	Most GHL users	$35/mo (50K emails)	Excellent
SendGrid	Established senders	$19.95/mo (50K)	Good
AWS SES	High volume, cost-sensitive	~$0.10/1K emails	Good (after sandbox)
Postmark	Transactional only	$15/mo (10K)	Good (no bulk marketing)
Self-hosted (Mailcow)	Cost control, agencies	~$5/mo VPS	Requires setup (guide)

For most GHL agencies, Mailgun is the right choice. It's the most tested integration, has reasonable pricing, and provides good deliverability dashboards.

Step 2: SMTP Configuration in GoHighLevel

1. Log into GoHighLevel → Settings → Email Services
2. Click Add SMTP or Connect Custom SMTP
3. Enter your provider's credentials:

Mailgun SMTP Settings

• Host: smtp.mailgun.org
• Port: 587
• Username: your Mailgun SMTP username (not your account email)
• Password: your Mailgun SMTP password
• Encryption: STARTTLS

SendGrid SMTP Settings

• Host: smtp.sendgrid.net
• Port: 587
• Username: apikey (literally the word "apikey")
• Password: your SendGrid API key
• Encryption: STARTTLS

AWS SES SMTP Settings

• Host: email-smtp.us-east-1.amazonaws.com (use your region)
• Port: 587
• Username: your SES SMTP username
• Password: your SES SMTP password
• Encryption: STARTTLS

Note: AWS SES starts in sandbox mode. You must request production access before sending to non-verified addresses.

Step 3: Domain Authentication

This is where most GHL setups fail. Your SMTP provider handles sending, but your domain's DNS must authenticate it.

For Mailgun:

1. Add your sending domain in Mailgun dashboard
2. Mailgun provides DNS records (SPF include, DKIM CNAME, CNAME tracking)
3. Add all records to your domain's DNS
4. Verify in Mailgun dashboard — all checks must pass

SPF Record Example (Mailgun + Google Workspace):

v=spf1 include:_spf.google.com include:mailgun.org -all

DMARC Record:

v=DMARC1; p=none; rua=mailto:[email protected]

Start with p=none, monitor for 2-4 weeks, then advance. See our DMARC guide for the full path.

The GoHighLevel SMTP Stats Problem

Here's what GHL support won't tell you: with custom SMTP, GoHighLevel only shows open and click events. Delivered, bounced, and deferred events are invisible inside GHL.

This means:

• You can't see bounce rates in GHL
• You can't see if emails were actually delivered
• You can't see deferrals or throttling

The Fix: Monitor at the Provider Level

• Mailgun: Dashboard → Logs & Analytics shows delivered, bounced, deferred, complained
• SendGrid: Activity → shows full delivery lifecycle
• AWS SES: CloudWatch metrics + SES event publishing

Build your monitoring workflow at the SMTP provider, not in GHL. GHL is your campaign tool, not your deliverability dashboard.

The Throttling Problem

GoHighLevel has a known issue: when you queue emails (bulk campaigns, workflows), GHL attempts to send them all at once through your SMTP provider. There's no built-in throttling.

This destroys deliverability when your SMTP provider has hourly or daily limits (which most do).

Workarounds:

1. Send in smaller batches — split campaigns into groups of 500-1,000
2. Use workflow delays — add 1-5 minute delays between sends in automation
3. Configure provider-side throttling — Mailgun allows per-domain rate limits
4. Use a provider without strict hourly limits — AWS SES scales better than Mailgun's lower tiers

Practitioner note: The throttling issue is the single biggest complaint I hear from GHL agencies. GHL treats your SMTP provider like an infinite pipe, but Mailgun's Flex plan only allows ~300 emails/hour by default. Either upgrade your Mailgun plan or batch your sends.

Practitioner note: If you're running a GHL agency with 10+ client sub-accounts, set up a dedicated sending domain and SMTP credentials per client. Sharing one SMTP account across clients means one bad sender poisons everyone's reputation.

Practitioner note: I've set up custom SMTP infrastructure for dozens of GHL agencies. The setup takes 2-3 hours to do correctly. The deliverability improvement over LC Email is typically 15-30% better inbox placement within the first month.

Warming Up a New Domain in GHL

GoHighLevel has no warmup feature. You have to do it manually:

Week 1: Send to 50-100 of your most engaged contacts per day. Use personal, conversational emails — not templates.

Week 2: Increase to 200-300/day. Continue with engaged contacts only.

Week 3: 500-1,000/day. Start including moderately engaged contacts.

Week 4: 2,000-5,000/day. Begin normal campaign sending to engaged segments.

Do not use GHL's bulk campaign feature during warmup. The volume spikes will burn your domain.

Monitor at your SMTP provider's dashboard throughout. Watch for bounce rate spikes, complaint rate increases, or deferrals.

This is where most GHL agencies get stuck — the platform doesn't solve your sending reputation, and their support can't help with SMTP infrastructure. If you need custom SMTP set up correctly for your GHL agency, book a consultation — I've configured infrastructure for dozens of GHL agencies and can have yours working within 48 hours.

Sources

• GoHighLevel: Email Services Documentation
• Mailgun: SMTP Credentials
• SendGrid: SMTP API
• AWS: SES SMTP Interface

---

v1.0 · March 2026