Interspire Email Marketer is a self-hosted PHP email marketing software with a long history serving agencies, ISPs, and organizations wanting full data ownership on their own servers. The unsubscribe mechanism uses the %%UNSUBSCRIBELINK%% merge tag auto-injected into every campaign footer, and Interspire supports RFC 8058 header injection when configured in the sending settings. Suppression is tracked at the list level with account-wide variant available. This guide covers the tag, the self-hosted responsibilities, and how to verify the setup end to end.
Interspire unsubscribe link
| Tag syntax | %%UNSUBSCRIBELINK%% |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with account-wide suppression |
| Config path | Settings > Send settings > List-Unsubscribe headers |
| RFC 8058 one-click | Manual toggle in Interspire send settings |
How to add the unsubscribe tag in Interspire
Place the merge tag exactly as shown below in the email template. Interspire 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
Manual toggle in Interspire send settings 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.
Interspire self-hosted deployment means the sysadmin must enable RFC 8058 header injection in the send settings and verify SPF, DKIM, and DMARC alignment on the outbound MTA. Interspire has a long history and older installations may run legacy versions without RFC 8058 support; upgrade to a current version before relying on one-click compliance. Analogous to MailWizz, Mautic, Octeth, and Sendy self-hosted patterns.
Testing your Interspire unsubscribe link
- Send a test message to a controlled Gmail address you own via the Interspire 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 Interspire unsubscribe link (step by step)
Interspire default templates include the unsubscribe link in the footer, but custom HTML templates require the tag inserted manually.
- Open your campaign or template in the Interspire admin.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
%%UNSUBSCRIBELINK%%. Interspire replaces it at send time with a signed URL scoped to the subscriber. - Wrap it in an anchor:
<a href="%%UNSUBSCRIBELINK%%">Unsubscribe</a>. - Enable RFC 8058 header injection under Settings > Send settings > List-Unsubscribe headers.
- Send a test to a seed address and verify the rendered link routes to the Interspire-hosted preference page and the headers are present in the message source.
Self-hosted responsibilities and version considerations
Interspire self-hosted deployment means the sysadmin must enable RFC 8058 header injection in the send settings and verify SPF, DKIM, and DMARC alignment on the outbound MTA. Interspire has a long history and older installations may run legacy versions without RFC 8058 support; upgrade to a current version before relying on one-click compliance. Analogous to MailWizz, Mautic, Octeth, and Sendy self-hosted patterns where infrastructure configuration is the sender responsibility.
RFC 8058 one-click headers via sending settings
Interspire exposes RFC 8058 header injection as a sending settings toggle rather than an always-on default. Once enabled, the List-Unsubscribe and List-Unsubscribe-Post headers inject on every marketing send from domains authenticated via the outbound MTA. Sysadmins must verify SPF alignment, DKIM signing on the sending domain, and DMARC policy to complete the one-click compliance chain. Older installations may need MTA-side header injection if Interspire itself does not support the toggle.
Agency and ISP multi-account deployment
Interspire agency and ISP multi-account deployment separates client accounts at the database level. Each account maintains isolated suppression lists, sender profiles, and RFC 8058 configuration. Cross-account suppression is not the default: an unsubscribe on Client A does not suppress the contact on Client B (same email in multiple accounts). Configure cross-account rules only when regulatory or business expectations require unified opt-out enforcement.
Frequently Asked Questions
What is the Interspire unsubscribe tag?
The merge tag is %%UNSUBSCRIBELINK%%. Interspire replaces it at send time with a signed URL scoped to the subscriber. Use it inside an anchor: <a href="%%UNSUBSCRIBELINK%%">Unsubscribe</a>.
Does Interspire support one-click unsubscribe by default?
Only when the sending settings toggle is enabled and the installation runs a version supporting RFC 8058 headers. Older Interspire installations may lack native support; upgrade to a current version or configure MTA-side header injection.
Is Interspire still actively developed?
Interspire Email Marketer has had periods of active development and dormancy. Verify the current maintenance status before selecting Interspire for a new deployment. Alternative self-hosted options include Mautic, MailWizz, and Octeth.
Is Interspire self-hosted or SaaS?
Self-hosted PHP application. Sysadmins handle server hardening, TLS certificates, MTA tuning, backup, and log retention in exchange for full data ownership and control over sending infrastructure.
Do Interspire multi-accounts share suppression?
Not by default. Multi-account architecture isolates suppression per client account. Configure cross-account rules only when regulatory or business expectations require unified opt-out enforcement.
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.
