What self-hosted mail server works best with GoHighLevel?

Mailcow is the best option for GHL. It's Docker-based, includes Rspamd for spam filtering, auto-renews TLS certificates, and provides SMTP credentials that plug directly into GHL. Postal is a lighter alternative for send-only use cases.

How much does self-hosted SMTP cost?

VPS hosting: $5-20/month depending on provider and specs. Hetzner CX21 ($5/month) handles most agency volumes. No per-email fees. Compared to Mailgun at $35-275/month, self-hosted pays for itself in the first month.

Is self-hosted SMTP reliable enough for client email?

Yes, with proper setup and monitoring. Mailcow handles millions of emails monthly for many organizations. The risk: if the server goes down, you fix it. Mitigate with monitoring alerts and a hosted SMTP backup.

Do I need a dedicated IP for self-hosted SMTP?

Your VPS comes with a dedicated IP by default. The IP needs a clean reputation — check blacklists before deploying. Set up PTR (reverse DNS) through your VPS provider. Hetzner and OVH allow PTR configuration in their control panels.

Can I self-host SMTP if I'm not technical?

Not recommended. Self-hosted SMTP requires Linux command-line skills, Docker knowledge, DNS management, and the ability to troubleshoot mail delivery issues. If you can't SSH into a server confidently, stick with Mailgun or AWS SES.

Self-Hosted SMTP for GoHighLevel: Setup Guide

When Self-Hosted Makes Sense

Self-hosted SMTP eliminates per-email costs. The math is simple:

Volume/Month	Mailgun Cost	AWS SES Cost	Self-Hosted Cost
50,000	$35	$5	$5
100,000	$90	$10	$5
200,000	$165	$20	$5-10
500,000	$275	$50	$10-20

At 200K emails/month, self-hosted saves $155-160/month vs Mailgun. That's $1,860-1,920/year. See our Mailcow + GHL integration guide and Postal + GHL guide for setup.

Self-host when:

Sending 100K+ emails/month
Comfortable with Linux administration
Want maximum cost control
Agency with multiple high-volume clients

Don't self-host when:

Under 50K emails/month (savings don't justify effort)
No Linux experience on your team
Can't commit to ongoing maintenance
Need vendor support as a safety net

Choosing a Mail Server

Mailcow (Recommended)

Mailcow is the best self-hosted option for GHL:

Docker-based (easy deployment and updates)
Includes Rspamd (spam filtering)
Auto-renewing TLS via Let's Encrypt
Web UI for management
DKIM signing built-in
Active community

Minimum VPS specs: 2 vCPU, 4GB RAM, 40GB SSD

Postal

Postal is lighter weight, designed for transactional/outbound email:

Ruby-based, Docker deployment available
Built for high-volume sending
Lighter resource requirements
Less feature-rich than Mailcow
Better suited for send-only setups

Minimum VPS specs: 1 vCPU, 2GB RAM, 20GB SSD

Mail-in-a-Box

Simpler but more limited:

One-command install on Ubuntu
Good for basic setups
Less flexible than Mailcow
Limited to Debian/Ubuntu

VPS Provider Selection

Your VPS provider matters because IP reputation starts with the hosting company.

Provider	Monthly Cost	PTR Support	IP Reputation
Hetzner	$5-10	Yes	Good
OVH	$5-12	Yes	Good
Vultr	$6-12	Yes	Variable
DigitalOcean	$6-12	Yes	Variable

Avoid: AWS EC2 (port 25 blocked by default), cheap VPS providers with spam-heavy IP ranges.

Choose Hetzner or OVH — both have good IP reputations and straightforward PTR configuration.

Practitioner note: Before deploying anything, check your VPS IP against blacklists (MXToolbox, MultiRBL). I've received IPs from providers that were pre-blacklisted from previous tenants. It takes weeks to get delisted. Better to check first and request a new IP if needed.

Deployment: Mailcow on Hetzner

Step 1: Provision VPS

Create Hetzner account
Create CX21 server (2 vCPU, 4GB RAM, 40GB SSD)
Select Ubuntu 22.04 or Debian 12
Set hostname to your mail domain (e.g., mail.youragency.com)

Step 2: Configure PTR Record

In Hetzner's console:

Go to your server's networking tab
Set reverse DNS to mail.youragency.com

This must match your mail server's hostname.

Step 3: DNS Records

Before installing Mailcow, configure DNS:

mail.youragency.com.     A      YOUR_VPS_IP
youragency.com.          MX 10  mail.youragency.com.
youragency.com.          TXT    "v=spf1 ip4:YOUR_VPS_IP ~all"
_dmarc.youragency.com.   TXT    "v=DMARC1; p=none; rua=mailto:[email protected]"

DKIM records get added after Mailcow generates keys.

Step 4: Install Mailcow

SSH into your server and run:

cd /opt
git clone https://github.com/mailcow/mailcow-dockerized
cd mailcow-dockerized
./generate_config.sh

Enter your mail hostname when prompted. Then:

docker compose pull
docker compose up -d

Step 5: Configure Mailcow

Access the web UI at https://mail.youragency.com
Log in with default credentials (change immediately)
Add your sending domain
Copy the DKIM public key and add to DNS
Create a mailbox for GHL sending (e.g., [email protected])

Step 6: Connect to GoHighLevel

In GHL:

Settings > Email Services > Add SMTP
Host: mail.youragency.com
Port: 587
Username: [email protected]
Password: the mailbox password
Encryption: STARTTLS

Send a test email. Check headers for proper SPF, DKIM, and DMARC authentication.

Practitioner note: The entire deployment takes 2-3 hours for someone comfortable with Linux. I've templated the process for agencies — DNS records are copy-paste with just the domain and IP swapped. The biggest time sink is waiting for DNS propagation.

Adding Client Domains

For each GHL client, add their sending domain to Mailcow:

Mailcow UI > Configuration > Mail Setup > Domains > Add Domain
Enter client's sending subdomain (e.g., marketing.clientdomain.com)
Copy DKIM key, add to client's DNS
Add SPF record pointing to your server IP
Create a dedicated mailbox for this client
Configure in the client's GHL sub-account

This gives each client isolated SMTP credentials on your shared server while maintaining per-domain DKIM signing.

Monitoring and Maintenance

Daily Monitoring

Check Mailcow's web UI for queue status
Review Rspamd dashboard for outbound issues
Check server resource usage

Weekly Tasks

Review mail logs for delivery issues
Check blacklist status for your IP
Verify DNS records are intact

Monthly Tasks

Update Mailcow (docker compose pull && docker compose up -d)
Review storage usage
Audit sending domains and volumes

Alerting

Set up alerts for:

Server down (use UptimeRobot or similar)
Mail queue backing up
IP blacklisted
Disk space low

Backup and Failover

Backup Strategy

Daily backups of Mailcow data (/opt/mailcow-dockerized)
Store backups off-server (Hetzner Storage Box or S3)
Test restore procedure quarterly

Failover Plan

Keep a hosted SMTP provider as backup:

Maintain a Mailgun or SendGrid account
Pre-configure credentials in GHL as secondary
If your server goes down, switch GHL to the backup

Practitioner note: I run a secondary Mailgun account for every self-hosted setup I manage. It costs nothing if unused (pay-per-email). When a server needs maintenance or an IP gets temporarily listed, I flip clients to Mailgun within minutes. The 10-minute failover is worth the $0/month standby cost.

Common Problems

IP Blacklisted

Check MXToolbox for listings
Submit delisting requests
Investigate what triggered the listing
Consider requesting a new IP from your VPS provider

Mail Queue Building Up

Check server resources (CPU, RAM, disk)
Verify DNS is resolving correctly
Check if recipient servers are deferring
Review Rspamd for false-positive blocks

TLS Certificate Issues

Mailcow auto-renews via Let's Encrypt
If renewal fails, check DNS A record points to server
Verify port 80 is accessible for HTTP challenge

If you need help setting up self-hosted SMTP for your GHL agency, book a consultation. I'll deploy, configure, and test the infrastructure, then hand you a working system with documentation.

Sources

Mailcow: Official Documentation
Hetzner: Cloud Server Documentation
M3AAWG: Best Practices for Sending Infrastructure
MXToolbox: Blacklist Check

v1.0 · April 2026