Mumara is a self-hosted email marketing and SMTP delivery software serving developers and technical mid-market customers with campaign broadcast, transactional API, and full data ownership on customer infrastructure. The unsubscribe mechanism uses the [unsubscribe] merge tag placed in campaign templates, and Mumara emits RFC 8058 headers when configured with appropriate MTA header injection. Suppression is tracked at the list level. This guide covers the tag, the self-hosted model, and how to verify the setup end to end.
Mumara unsubscribe link
| Tag syntax | [unsubscribe] |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with self-hosted suppression |
| Config path | Admin > Sender profiles > Footer template |
| RFC 8058 one-click | Manual, requires MTA-side header injection configuration |
How to add the unsubscribe tag in Mumara
Place the merge tag exactly as shown below in the email template. Mumara replaces it at send time with a signed URL scoped to the recipient and campaign.
[unsubscribe]For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="[unsubscribe]">Unsubscribe from this list</a>Auto-embedded in every campaign footer
Manual, requires MTA-side header injection configuration 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.
Mumara self-hosted deployment requires sysadmin management for server, MTA (Postfix/Sendmail), DNS (SPF/DKIM/DMARC), TLS certificates, and backup rotation. RFC 8058 headers require MTA-side injection configuration since the application layer alone does not append them. Analogous to MailWizz, Mautic, Interspire, and Octeth self-hosted patterns. Full data ownership balances against operational burden.
Testing your Mumara unsubscribe link
- Send a test message to a controlled Gmail address you own via the Mumara 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 Mumara unsubscribe link (step by step)
- Open your campaign template in the Mumara admin.
- Add or edit a text block in the footer.
- Insert the merge tag
[unsubscribe]. - Wrap it in an anchor:
<a href="[unsubscribe]">Unsubscribe</a>. - Configure MTA-side List-Unsubscribe header injection for RFC 8058 compliance.
- Send a test to a seed address and verify the rendered link routes to the Mumara-hosted preference page.
Self-hosted deployment model
Mumara self-hosted deployment requires sysadmin management for server, MTA (Postfix/Sendmail), DNS (SPF/DKIM/DMARC), TLS certificates, and backup rotation. Full data ownership balances against operational burden. Analogous to MailWizz, Mautic, Interspire, and Octeth self-hosted patterns. Suitable for developers and agencies wanting complete control over sending infrastructure and unlimited sending volume at fixed license cost.
RFC 8058 requires MTA-side configuration
Mumara RFC 8058 headers require MTA-side injection configuration since the application layer alone does not append them. Postfix milters or Sendmail plugins add List-Unsubscribe and List-Unsubscribe-Post headers matching the unsubscribe URL in the message body. Verify SPF, DKIM, and DMARC on the sending domain for Google February 2024 bulk sender compliance. Self-hosted deployments are responsible for header injection alignment.
SMTP delivery software and unlimited sending
Mumara SMTP delivery software combines campaign broadcast and SMTP relay on the customer server. Unlimited sending volume at fixed license cost differentiates from usage-based SaaS pricing. High-volume senders may benefit from cost savings compared to cloud ESPs, though operational costs (server, monitoring, IP warm-up, sender reputation management) should be included in total cost calculation.
Frequently Asked Questions
What is the Mumara unsubscribe tag?
The merge tag is [unsubscribe]. Mumara replaces it at send time with a signed URL scoped to the subscriber.
Does Mumara support one-click unsubscribe automatically?
Not automatically. MTA-side List-Unsubscribe header injection is required (Postfix milter or Sendmail plugin). Self-hosted deployments configure header injection at the MTA layer.
Who manages the Mumara server?
The customer sysadmin team. Full data ownership means full operational responsibility for server, MTA, DNS, TLS certificates, and backups.
Is Mumara unlimited sending truly unlimited?
License-wise yes, but operational limits apply: server capacity, IP sending reputation, MTA throughput, and recipient inbox provider throttling all impose practical limits.
How does Mumara compare to MailWizz or Interspire?
All three are self-hosted PHP email platforms. Mumara emphasizes SMTP delivery. MailWizz focuses on campaign broadcast. Interspire is legacy with long history. Vendor choice depends on feature priorities and pricing model.
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.
