MailRush is a cold email outreach platform serving sales teams and agencies with dedicated IP infrastructure, warm-up automation, and deliverability-focused sending for outbound sales campaigns. The unsubscribe mechanism uses the {unsubscribe_link} merge tag placed in email templates, and MailRush emits RFC 8058 headers automatically for authenticated sending domains. Suppression is tracked at the contact level with cross-campaign enforcement. This guide covers the tag, the cold outreach model, and how to verify the setup end to end.
Mailrush Io unsubscribe link
| Tag syntax | {unsubscribe_link} |
| Placement | Manual placement in cold outreach templates |
| Scope | Contact-level opt-out with cross-campaign suppression |
| Config path | Campaigns > Templates > Footer configuration |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Mailrush Io
Place the merge tag exactly as shown below in the email template. Mailrush Io replaces it at send time with a signed URL scoped to the recipient and campaign.
{unsubscribe_link}For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="{unsubscribe_link}">Unsubscribe from this list</a>Manual placement in cold outreach templates
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.
MailRush cold email use case means outreach targets have not opted in explicitly; unsubscribe links become critical for compliance with US CAN-SPAM, EU GDPR legitimate interest B2B interpretation, and CASL express consent requirements. Configure per-jurisdiction sending practices carefully since cold outreach compliance varies significantly between US CAN-SPAM (permissive) and EU GDPR (strict). Dedicated IP infrastructure requires warm-up before scaling.
Testing your Mailrush Io unsubscribe link
- Send a test message to a controlled Gmail address you own via the Mailrush Io 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 MailRush unsubscribe link (step by step)
- Open your cold outreach template in the MailRush editor.
- Add or edit a text block in the footer.
- Insert the merge tag
{unsubscribe_link}. - Wrap it in an anchor:
<a href="{unsubscribe_link}">Unsubscribe</a>. - Configure the sender identity under Campaigns > Templates > Footer configuration.
- Send a test to a seed address and verify the rendered link routes to the MailRush-hosted preference page.
Cold outreach compliance model
MailRush cold email use case means outreach targets have not opted in explicitly; unsubscribe links become critical for compliance with US CAN-SPAM, EU GDPR legitimate interest B2B interpretation, and CASL express consent requirements. Configure per-jurisdiction sending practices carefully since cold outreach compliance varies significantly between US CAN-SPAM (permissive) and EU GDPR (strict). Dedicated IP infrastructure requires warm-up before scaling to preserve sender reputation.
RFC 8058 one-click headers
MailRush 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 send from domains authenticated under Campaigns > Templates. SPF and DKIM records must be verified. Cold outreach senders benefit from RFC 8058 to maintain inbox placement despite non-opt-in recipient base.
Dedicated IP infrastructure and warm-up
MailRush dedicated IP infrastructure gives cold outreach senders control over sender reputation independent of shared IP pools. IP warm-up automation gradually ramps sending volume to build reputation with inbox providers. Opt-out events tracked at the contact level enforce cross-campaign suppression, preventing re-outreach to unsubscribed contacts across different sales sequences.
Frequently Asked Questions
What is the MailRush unsubscribe tag?
The merge tag is {unsubscribe_link}. MailRush replaces it at send time with a signed URL scoped to the contact.
Is cold email legal without opt-in?
Depends on jurisdiction. US CAN-SPAM allows cold email with sender identification and functional unsubscribe. EU GDPR requires legitimate interest justification for B2B. CASL requires express consent (strictest).
Does MailRush support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. MailRush injects List-Unsubscribe and List-Unsubscribe-Post headers on every send.
How long does IP warm-up take on MailRush?
Typically 4-8 weeks depending on target volume. Gradual ramp-up preserves sender reputation with Gmail, Yahoo, and Microsoft inbox providers.
How does MailRush compare to Snov.io or Hexospark?
All three target cold outreach. MailRush emphasizes dedicated IP infrastructure. Snov.io adds email finder and verifier. Hexospark integrates LinkedIn. Vendor choice depends on channel and infrastructure priorities.
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.
