Feature Request: Add RFC-Compliant List-Unsubscribe Headers for Custom SMTP (Amazon SES)
K
Kevin Hood
Product Area: Email (LC Email / Custom SMTP)
Priority: High (Deliverability & Compliance)
Use Case: High-volume transactional and broadcast email using Amazon SES
Summary
When using LC Email with Mailgun, GoHighLevel correctly includes RFC-compliant List-Unsubscribe headers.
However, when using Amazon SES as a custom SMTP provider, these headers are not included, which creates deliverability and compliance issues for bulk senders.
This makes Amazon SES impractical for production email sending despite being a supported SMTP option.
Current Behavior
LC Email (Mailgun integration) Sends:
|| List-Unsubscribe: <mailto:...>, <https://...>
|| List-Unsubscribe-Post: List-Unsubscribe=One-Click
-> Gmail/Yahoo display native “Unsubscribe” UI
-> Complies with Google/Yahoo 2024 bulk sender requirements
Custom SMTP (Amazon SES):
-> No List-Unsubscribe headers are sent
-> Gmail does NOT show native unsubscribe
-> Unsubscribes rely solely on footer links
-> Increases spam complaints and suppresses inbox placement
-> Fails Google/Yahoo bulk sender expectations
Why This Matters (Deliverability Impact)
As of 2024, Gmail and Yahoo require bulk senders to:
• Support one-click unsubscribe
• Include List-Unsubscribe and List-Unsubscribe-Post headers
• Provide frictionless opt-out without login or extra steps
Without these headers:
• Inbox placement is negatively impacted
• Complaint rates increase
• Sender reputation degrades over time
• High-volume senders cannot safely use SES via GHL
This affects:
• Agencies
• Newsletter businesses
• Daily senders
• High-volume broadcast workflows
Requested Enhancement
When using custom SMTP providers (Amazon SES), please:
Inject RFC-compliant headers into all outbound emails:
|| List-Unsubscribe: <mailto:unsubscribe@domain.com>,
|| List-Unsubscribe-Post: List-Unsubscribe=One-Click
Allow the unsubscribe URL to:
• Respect existing GHL unsubscribe logic
• Mark contacts as unsubscribed immediately
• Work without authentication
Apply this consistently across:
• Broadcasts
• Automations
• Campaign emails
This should mirror existing behavior in the Mailgun (LC Email) integration.
Additional Context
-> Amazon SES fully supports List-Unsubscribe headers
-> This feature works correctly today in many ESPs (FluentCRM, Email Octopus, Mail Mint, Sure Contacts etc...)
It's already possible to handle bounces via Make.com + SES event notifications.
This change would make SES viable as a long-term sending option inside GHL
Business Impact for GoHighLevel
Adding this feature would:
-> Reduce LC Email cost objections for high-volume senders
-> Improve deliverability outcomes platform-wide
-> Reduce spam complaints and support tickets
-> Enable agencies to use SES at scale without compromising compliance
-> Align GHL with modern bulk sender standards
Closing
This is not a workaround request — it’s a core deliverability requirement for custom SMTP usage in 2024+.
Parity with the Mailgun integration would unlock SES as a first-class sending option inside GoHighLevel.
Thank you for considering this.
Log In