EzyMsg is an SMS and email marketing platform serving Southeast Asian and Australian SMBs with unified multi-channel messaging, transactional API, and regional deliverability. The unsubscribe mechanism uses the {UNSUBSCRIBE} merge tag auto-injected into every campaign footer, and EzyMsg emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the list level with SEA PDPA and Australian Spam Act enforcement. This guide covers the tag, the SMS-first heritage, and how to verify the setup end to end.
EzyMsg unsubscribe link
| Tag syntax | {UNSUBSCRIBE} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with SEA/AU regional enforcement |
| Config path | Settings > Sender identity > Footer |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in EzyMsg
Place the merge tag exactly as shown below in the email template. EzyMsg 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
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.
EzyMsg SMS-first heritage means SMS opt-out via STOP keyword is honored immediately per SEA and Australian regulatory expectations. Email opt-out and SMS opt-out are tracked separately by default since per-channel consent granularity matches SEA PDPA and Australian Spam Act 2003. Configure unified cross-channel suppression only when business or regulatory expectations require it.
Testing your EzyMsg unsubscribe link
- Send a test message to a controlled Gmail address you own via the EzyMsg 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 EzyMsg unsubscribe link (step by step)
- Open your campaign in the EzyMsg editor.
- 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 the sender identity under Settings > Sender identity > Footer.
- Send a test to a seed address and verify the rendered link routes to the EzyMsg-hosted preference page.
SMS-first heritage and per-channel opt-out
EzyMsg SMS-first heritage means SMS opt-out via STOP keyword is honored immediately per SEA and Australian regulatory expectations. Email opt-out and SMS opt-out are tracked separately by default since per-channel consent granularity matches SEA PDPA and Australian Spam Act 2003. Configure unified cross-channel suppression only when business or regulatory expectations require it. Regional deliverability infrastructure supports Singapore, Malaysia, Thailand, Indonesia, and Australian mobile carriers.
RFC 8058 one-click headers
EzyMsg 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.
Regional SEA and Australia deliverability
EzyMsg regional deliverability infrastructure peers with Singapore, Malaysia, Thailand, Indonesia, and Australian carriers for SMS routing and inbox providers for email. Regional peering typically improves inbox and SMS delivery placement for SEA and AU audiences compared to US-based platforms sending cross-region. Per-country PDPA and Australian Spam Act 2003 compliance is enforced at the account level.
Frequently Asked Questions
What is the EzyMsg unsubscribe tag?
The merge tag is {UNSUBSCRIBE}. EzyMsg replaces it at send time with a signed URL scoped to the subscriber.
Does email opt-out stop SMS on EzyMsg?
Not by default. Per-channel consent granularity under SEA PDPA and Australian Spam Act. Configure unified cross-channel suppression only when business expectations require it.
Does EzyMsg support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. EzyMsg injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send.
Is STOP keyword handled automatically on EzyMsg?
Yes. SMS opt-out via STOP is honored immediately per SEA and Australian regulatory expectations. Contact removed from SMS sends future.
How does EzyMsg compare to Vision6 or MyGuestlist for Australia?
EzyMsg emphasizes SMS+email multi-channel for SEA/AU. Vision6 targets Australian SMB email. MyGuestlist focuses on venue/hospitality vertical. Vendor choice depends on channel needs and vertical fit.
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.
