MailBluster is a cost-effective email marketing platform built on top of Amazon SES infrastructure, popular with cost-conscious SMBs and developers looking for SES pricing with a friendly user interface. The unsubscribe mechanism uses the {{unsubscribeLink}} merge variable auto-injected into every campaign footer, and MailBluster supports RFC 8058 header injection through the underlying SES Configuration Set. Consent is tracked at the list level with an account-wide suppression variant. This guide covers the tag, the SES-based architecture, and how to verify the setup end to end.
MailBluster unsubscribe link
| Tag syntax | {{unsubscribeLink}} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with account-wide suppression |
| Config path | Settings > Amazon SES > Configuration Set |
| RFC 8058 one-click | Via SES Configuration Set with List-Unsubscribe headers enabled |
How to add the unsubscribe tag in MailBluster
Place the merge tag exactly as shown below in the email template. MailBluster replaces it at send time with a signed URL scoped to the recipient and campaign.
{{unsubscribeLink}}For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="{{unsubscribeLink}}">Unsubscribe from this list</a>Auto-embedded in every campaign footer
Via SES Configuration Set with List-Unsubscribe headers enabled The recipient's mailbox provider (Gmail, Yahoo) uses the List-Unsubscribe-Post header to expose the native one-click button on the message. Requires domain authentication with DKIM and DMARC.
MailBluster runs on customer-configured Amazon SES accounts, meaning RFC 8058 compliance depends on the SES Configuration Set configuration. Enable Custom MAIL FROM domain and the List-Unsubscribe headers option in the Configuration Set to inject compliance headers. Missing SES-level configuration silently falls out of one-click compliance regardless of MailBluster UI settings.
Testing your MailBluster unsubscribe link
- Send a test message to a controlled Gmail address you own via the MailBluster campaign preview action
- Click the footer unsubscribe link and confirm the opt-out on the landing page
- Check the subscriber or contact record: the status should be Unsubscribed within seconds
- Verify the RFC 8058 headers in Gmail: open the message, click three dots, then Show original. Look for
List-UnsubscribeandList-Unsubscribe-Post: List-Unsubscribe=One-Click
Want the full 222-platform reference?
See the pillar guide with the compliance landscape, the RFC 8058 deep dive, and the unsubscribe tag for every ESP: How to add an unsubscribe link: the complete 2026 guide →
How to add the MailBluster unsubscribe link (step by step)
MailBluster drag-and-drop templates include the unsubscribe link in the default footer, but custom HTML templates require the tag inserted manually.
- Open your campaign or template in the MailBluster editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge variable
{{unsubscribeLink}}. MailBluster replaces it at send time with a signed URL scoped to the subscriber. - Wrap it in an anchor:
<a href="{{unsubscribeLink}}">Unsubscribe</a>. - Configure the Amazon SES Configuration Set under Settings > Amazon SES to enable List-Unsubscribe headers.
- Send a test to a seed address and verify the rendered link routes to the MailBluster-hosted unsubscribe confirmation page.
SES Configuration Set and RFC 8058
MailBluster runs on customer-configured Amazon SES accounts, meaning RFC 8058 compliance depends on the SES Configuration Set configuration. Enable Custom MAIL FROM domain and the List-Unsubscribe headers option in the Configuration Set to inject compliance headers. Missing SES-level configuration silently falls out of one-click compliance regardless of MailBluster UI settings. This is the fundamental architectural difference from full-service SaaS ESPs: MailBluster provides the UI and orchestration, but the sending infrastructure is customer-owned SES.
Cost model and unlimited plans
MailBluster cost model leverages Amazon SES pricing directly, letting cost-conscious SMBs and developers send at SES infrastructure prices (typically $0.10 per 1000 emails) with a MailBluster subscription for the UI and features on top. This is significantly cheaper than full-service ESPs at scale but requires customer AWS account setup, SES production access approval, and SES bounce and complaint handling configuration. For pure transactional apps, direct SES API is often simpler; for marketing sends with UI orchestration, MailBluster adds real value.
Suppression sync between MailBluster and SES
MailBluster tracks opt-outs at the list level in the MailBluster database, but SES also maintains its own account-level suppression list for hard bounces and complaint feedback. Keep SES suppression synced with MailBluster by enabling automatic SNS notification handling: SES publishes bounce and complaint events to SNS, and MailBluster subscribes to update the local suppression list. Missing this sync can cause deliverability degradation as unsubscribed contacts continue receiving sends until SES suppression catches up.
Frequently Asked Questions
What is the MailBluster unsubscribe tag?
The merge variable is {{unsubscribeLink}}. MailBluster replaces it at send time with a signed URL scoped to the subscriber. Use it inside an anchor: <a href="{{unsubscribeLink}}">Unsubscribe</a>.
Does MailBluster support one-click unsubscribe for Gmail and Yahoo?
Yes when the underlying Amazon SES Configuration Set is configured for List-Unsubscribe headers. Missing SES-level configuration silently falls out of one-click compliance regardless of MailBluster UI settings. Configure both layers correctly.
Is MailBluster cheaper than SendGrid or Mailchimp?
Yes at scale, since MailBluster leverages Amazon SES infrastructure pricing (typically $0.10 per 1000 emails) plus a MailBluster subscription. Below 10,000 emails per month, the difference is smaller due to fixed subscription costs.
How does MailBluster handle SES bounce and complaint feedback?
Via SNS notification subscription. SES publishes bounce and complaint events to SNS; MailBluster subscribes to update the local suppression list. Enable this sync during initial setup to prevent suppression drift between MailBluster and SES account-level suppression.
Do I need SES production access for MailBluster?
Yes for any real production sending. SES sandbox limits sends to verified addresses only, which is not usable for marketing sends. Request SES production access via the AWS console before setting up MailBluster campaigns.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
