ReachMail is a US-based email marketing platform serving SMBs and mid-market brands with drag-and-drop editor, list management, and standard automation flows. The unsubscribe mechanism uses the [ReachMail-Unsubscribe] merge tag auto-injected into every campaign footer, and ReachMail emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the list level with subscriber-level opt-out. This guide covers the tag, the US CAN-SPAM baseline, and how to verify the setup end to end.
Reachmail unsubscribe link
| Tag syntax | [ReachMail-Unsubscribe] |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with account-wide suppression option |
| Config path | Settings > Sender identity > Footer template |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Reachmail
Place the merge tag exactly as shown below in the email template. Reachmail replaces it at send time with a signed URL scoped to the recipient and campaign.
[ReachMail-Unsubscribe]For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="[ReachMail-Unsubscribe]">Unsubscribe from this list</a>Auto-embedded in every campaign footer
Yes, automatic for authenticated sending domains 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.
ReachMail uses a distinctive bracket-with-branded-name merge tag ([ReachMail-Unsubscribe]) rather than generic conventions. Template migration to or from ReachMail requires tag conversion. US CAN-SPAM compliance is the default baseline; senders targeting EU or Canadian audiences should configure double opt-in and consent documentation practices matching GDPR or CASL respectively.
Testing your Reachmail unsubscribe link
- Send a test message to a controlled Gmail address you own via the Reachmail 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 ReachMail unsubscribe link (step by step)
ReachMail 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 ReachMail editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
[ReachMail-Unsubscribe]. ReachMail replaces it at send time with a signed URL scoped to the subscriber. - Wrap it in an anchor:
<a href="[ReachMail-Unsubscribe]">Unsubscribe</a>. - Configure the sender identity under Settings > Sender identity > Footer template.
- Send a test to a seed address and verify the rendered link routes to the ReachMail-hosted preference page.
Branded merge tag syntax and template migration
ReachMail uses a distinctive bracket-with-branded-name merge tag ([ReachMail-Unsubscribe]) rather than generic conventions. Template migration to or from ReachMail requires tag conversion. Custom HTML templates copied from other ESPs must be updated to use the ReachMail-specific tag format. This is different from generic square-bracket syntax used by some legacy ESPs, and the branded prefix helps prevent accidental collisions with other placeholder systems.
RFC 8058 one-click headers
ReachMail added RFC 8058 one-click unsubscribe automatically ahead of the Google and Yahoo February 2024 requirements. The List-Unsubscribe and List-Unsubscribe-Post headers inject on every marketing send from domains authenticated under Settings > Sender identity. SPF and DKIM records must be verified. US data residency is the default.
US CAN-SPAM baseline and international considerations
ReachMail US CAN-SPAM compliance is the default baseline: physical postal address in the footer, honest From line, unsubscribe within 10 business days. Senders targeting EU or Canadian audiences should configure double opt-in and consent documentation practices matching GDPR or CASL respectively, since CAN-SPAM alone does not satisfy those stricter frameworks. Automation flows respect the subscriber opt-out flag at every send step, matching CAN-SPAM 10-business-day suppression requirement.
Frequently Asked Questions
What is the ReachMail unsubscribe tag?
The merge tag is [ReachMail-Unsubscribe]. ReachMail replaces it at send time with a signed URL scoped to the subscriber. Use it inside an anchor: <a href="[ReachMail-Unsubscribe]">Unsubscribe</a>.
Does ReachMail support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. ReachMail injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified under Settings > Sender identity.
Does ReachMail enforce GDPR double opt-in?
Not by default (US CAN-SPAM baseline). Senders targeting EU audiences should configure double opt-in and consent documentation practices manually to satisfy GDPR expectations, which are stricter than CAN-SPAM.
Do ReachMail automations respect opt-outs?
Yes. Automation flows respect the subscriber opt-out flag at every send step, matching CAN-SPAM 10-business-day suppression requirement. An unsubscribed subscriber exits all flows automatically.
Is ReachMail data hosted in the US?
Yes, US data residency is the default. Senders targeting EU or Canadian audiences with data localization requirements should evaluate whether the US default matches their regulatory expectations for cross-border data transfer.
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.
