Octeth (formerly Oempro) is a self-hosted email marketing platform popular with agencies, ISPs, and organizations wanting full data ownership and on-premises deployment control. The unsubscribe mechanism uses the [SUBSCRIBER_UNSUBSCRIBE_URL] merge tag auto-injected into every campaign footer, and Octeth supports RFC 8058 header injection when configured in the sending engine settings. Suppression is tracked at the list level with account-wide variant available. This guide covers the tag, the self-hosted architecture, and how to verify the setup end to end.
Octeth unsubscribe link
| Tag syntax | [SUBSCRIBER_UNSUBSCRIBE_URL] |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with account-wide suppression |
| Config path | Settings > Sending engine > List-Unsubscribe headers |
| RFC 8058 one-click | Manual toggle in sending engine settings |
How to add the unsubscribe tag in Octeth
Place the merge tag exactly as shown below in the email template. Octeth replaces it at send time with a signed URL scoped to the recipient and campaign.
[SUBSCRIBER_UNSUBSCRIBE_URL]For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="[SUBSCRIBER_UNSUBSCRIBE_URL]">Unsubscribe from this list</a>Auto-embedded in every campaign footer
Manual toggle in sending engine 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.
Octeth self-hosted deployment means the sysadmin must enable RFC 8058 header injection in the sending engine settings and verify SPF, DKIM, and DMARC alignment on the outbound MTA. Missing the toggle silently falls out of one-click compliance regardless of template configuration. Analogous to Mautic, MailWizz, and Sendy self-hosted patterns where infrastructure configuration is the sender responsibility.
Testing your Octeth unsubscribe link
- Send a test message to a controlled Gmail address you own via the Octeth 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 Octeth unsubscribe link (step by step)
Octeth 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 Octeth admin.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
[SUBSCRIBER_UNSUBSCRIBE_URL]. Octeth replaces it at send time with a signed URL scoped to the subscriber. - Wrap it in an anchor:
<a href="[SUBSCRIBER_UNSUBSCRIBE_URL]">Unsubscribe</a>. - Enable RFC 8058 header injection under Settings > Sending engine > List-Unsubscribe headers.
- Send a test to a seed address and verify the rendered link routes to the Octeth-hosted preference page and the headers are present in the message source.
Self-hosted deployment and sysadmin responsibilities
Octeth self-hosted deployment means the sysadmin must enable RFC 8058 header injection in the sending engine settings and verify SPF, DKIM, and DMARC alignment on the outbound MTA. Missing the toggle silently falls out of one-click compliance regardless of template configuration. Analogous to Mautic, MailWizz, and Sendy self-hosted patterns where infrastructure configuration is the sender responsibility. Server hardening, TLS certificates, MTA tuning, and log retention all fall on the sysadmin, in exchange for full data ownership and control.
RFC 8058 one-click headers via sending engine toggle
Octeth exposes RFC 8058 header injection as a sending engine 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 (softfail or pass), DKIM signing on the sending domain, and DMARC policy (at minimum p=none for reporting) to complete the one-click compliance chain.
Agency and ISP multi-tenant deployment
Octeth agency and ISP multi-tenant deployment separates client tenants at the database and sending engine level. Each tenant maintains isolated suppression lists, sender profiles, and RFC 8058 configuration. Cross-tenant suppression is not the default: an unsubscribe on Client A does not suppress the contact on Client B (same email in multiple tenants). Configure cross-tenant rules only when regulatory or business expectations require unified opt-out enforcement across tenants.
Frequently Asked Questions
What is the Octeth unsubscribe tag?
The merge tag is [SUBSCRIBER_UNSUBSCRIBE_URL]. Octeth replaces it at send time with a signed URL scoped to the subscriber. Use it inside an anchor: <a href="[SUBSCRIBER_UNSUBSCRIBE_URL]">Unsubscribe</a>.
Does Octeth support one-click unsubscribe by default?
Only when the sending engine toggle is enabled. Missing the toggle silently falls out of one-click compliance regardless of template configuration. Sysadmins must also verify SPF, DKIM, and DMARC alignment on the outbound MTA.
Is Octeth the same as Oempro?
Yes, Octeth is the rebranded successor to Oempro. Legacy Oempro deployments continue functioning under the Octeth product line. Documentation and support have consolidated under the Octeth branding.
Is Octeth self-hosted or SaaS?
Self-hosted with on-premises or private cloud deployment. Full data ownership and infrastructure control in exchange for sysadmin responsibilities (server hardening, TLS certificates, MTA tuning, log retention).
Do Octeth agency tenants share suppression?
Not by default. Multi-tenant architecture isolates suppression per client tenant. Configure cross-tenant 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.
