GoHighLevel Email Throttling: The Queue Problem and Solutions

The Problem

You create a campaign in GoHighLevel targeting 5,000 contacts. You hit send. GHL attempts to deliver all 5,000 messages to your SMTP server within minutes.

Your Mailgun Foundation plan allows ~300 emails per hour. GHL doesn't know or care about this limit. It dumps 5,000 messages as fast as it can.

Result: the first ~300 deliver. The rest queue, defer, or fail. Some recipients get the email immediately, some get it 6 hours later, some never get it. Your SMTP provider's dashboard shows a mess of deferrals and errors.

This is the GHL throttling problem. It affects every agency using custom SMTP for bulk campaigns. See our throttling workarounds guide and high-volume GHL guide for solutions.

SMTP Provider Rate Limits

Provider	Plan	Approx Rate Limit
Mailgun Foundation	$35/mo	~300-500/hour
Mailgun Scale	$90/mo	Higher (contact support for exact)
SendGrid Essentials	$19.95/mo	Varies by account age
SendGrid Pro	$89.95/mo	Higher limits
AWS SES	Pay-per-email	1-14/second (adjustable, request increase)
Google Workspace	$6/user/mo	500/day (DO NOT use for bulk)
Microsoft 365	$6/user/mo	10,000/day, 30/minute

GHL doesn't respect any of these limits. You must manage it yourself.

Solutions

Solution 1: Smaller Batches (Easiest)

Instead of one campaign to 5,000 contacts:

1. Create 5 segments of 1,000 each
2. Send to segment 1 immediately
3. Wait 30-60 minutes
4. Send to segment 2
5. Repeat

This keeps each burst within your provider's hourly limit.

Downside: Manual work. Doesn't scale well with daily campaigns.

Solution 2: Workflow Delays

For workflow-triggered sends (not bulk campaigns):

1. Add a Wait step between email actions
2. Set wait to 1-5 minutes
3. This staggers sends across time instead of bursting

Trigger → Wait 1 min → Send Email 1 → Wait 5 min → Send Email 2

Downside: Only works for workflows, not bulk campaigns. Adds latency.

Solution 3: Upgrade SMTP Plan

Move to a higher-tier plan that handles burst volume:

• Mailgun: Scale plan ($90/mo) has higher throughput than Foundation
• SendGrid: Pro plan ($89.95/mo) handles more volume
• AWS SES: Request sending rate increase (up to 50K/second with approval)

Downside: Costs more. Doesn't eliminate the root issue.

Solution 4: Provider-Side Rate Limiting

Some SMTP providers allow per-domain rate configuration:

• Mailgun: Contact support to set per-domain rate limits
• Self-hosted (Postfix): Configure smtpd_client_message_rate_limit
• Self-hosted (Postal): Configure rate limits in server settings

This tells the provider to accept messages from GHL and queue them internally, delivering at a controlled rate.

Best solution when combined with a provider that handles queuing well.

Solution 5: Self-Hosted SMTP with Built-in Throttling

Self-hosted options (Postal, Mailcow with Postfix) let you configure:

• Message rate limits per domain
• Concurrent connection limits per destination
• Queue management for controlled delivery

GHL can dump messages as fast as it wants. Your self-hosted server queues them and delivers at a controlled, ISP-friendly rate.

Best long-term solution for high-volume agencies.

The Real Impact

Throttling isn't just about convenience. Uncontrolled burst sending:

1. Triggers ISP rate limiting. Gmail, Outlook, Yahoo defer messages from bursty senders
2. Damages reputation. Sudden volume spikes look like spam behavior
3. Causes delivery failures. Provider rejects messages that exceed rate limits
4. Creates inconsistent delivery timing. Some contacts get the email immediately, others hours later

For time-sensitive campaigns (flash sales, event announcements), inconsistent delivery timing directly impacts revenue.

Practitioner note: The throttling problem is the #2 complaint I hear from GHL agencies (after deliverability on LC Email). The fix depends on volume: under 5K per campaign, smaller batches work. Over 5K per campaign consistently, self-hosted SMTP with queue management is the right answer. Mailgun/SendGrid rate limits become a constraint at agency scale.

Practitioner note: For agencies running Black Friday/Cyber Monday campaigns through GHL: plan your SMTP capacity in advance. A 50K-contact campaign that GHL fires all at once will overwhelm a Mailgun Foundation plan for hours. Either upgrade temporarily, pre-segment into batches, or use self-hosted SMTP with queue management.

If you need GHL email infrastructure that handles burst sending without throttling issues, schedule a consultation — I design SMTP architecture specifically for GHL agencies.

Sources

• GoHighLevel: Email Services
• Mailgun: Rate Limits

---

v1.0 · March 2026