Cakemail is a Canadian email marketing platform with a French deployment (Cakemail FR) focused on transactional-friendly bulk sends for small businesses, franchises, and agencies serving multi-brand customers. The unsubscribe mechanism uses the [unsubscribe] merge tag auto-injected into every campaign footer. Cakemail emits RFC 8058 headers automatically once the sending domain is authenticated. Contact opt-out is tracked per mailing list, with an opt-out from all link available via a separate merge tag. This guide covers the tag, the FR deployment specifics, and how to verify the setup end to end.
Cakemail Fr unsubscribe link
| Tag syntax | [unsubscribe] |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with global opt-out variant available |
| Config path | Account > Settings > Email footer template |
| RFC 8058 one-click | Yes, automatic once sending domain is authenticated |
How to add the unsubscribe tag in Cakemail Fr
Place the merge tag exactly as shown below in the email template. Cakemail Fr 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 once sending domain is authenticated 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.
Cakemail FR uses a separate account infrastructure from Cakemail primary despite being the same product. Contacts, suppression lists, and templates are not shared across the two deployments. Multi-country senders using both must sync opt-outs manually via API or middleware to avoid sending to a contact who unsubscribed from the other deployment.
Testing your Cakemail Fr unsubscribe link
- Send a test message to a controlled Gmail address you own via the Cakemail Fr 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 Cakemail FR unsubscribe link (step by step)
Cakemail FR templates include the unsubscribe link in the default footer, but custom HTML templates require the tag inserted manually.
- Open your campaign or template in the Cakemail FR editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
[unsubscribe]. Cakemail replaces it at send time with a signed URL unique per subscriber. - Wrap it in an anchor with your preferred label:
<a href="[unsubscribe]">Se désabonner</a>for French audiences. - Add the physical postal address block. Cakemail reads it from Account > Settings > Sender identity.
- Send a test to a seed address and verify the rendered link routes to the Cakemail-hosted preference page.
Cakemail FR vs Cakemail primary deployments
Cakemail FR uses a separate account infrastructure from Cakemail primary despite being the same product. Contacts, suppression lists, and templates are not shared across the two deployments. Multi-country senders using both Cakemail FR and Cakemail primary must sync opt-outs manually via API or middleware to avoid sending to a contact who unsubscribed from the other deployment. Choose the deployment that matches your primary market: Cakemail FR for French, Belgian, and Swiss audiences.
RFC 8058 one-click headers
Cakemail 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 Account > Sender identity. SPF and DKIM records must be verified. The Canadian data residency (with French compliance option) means Cakemail is well-suited for GDPR and CASL dual compliance for senders operating in both EU and Canadian markets.
Franchise and agency multi-brand model
Cakemail Sub-Account architecture supports agencies and franchises managing multi-brand sends under one master account. Each Sub-Account has isolated subscribers, templates, and suppression lists, letting a franchise headquarters delegate email sending to local franchisees while maintaining compliance segregation. This is the fundamental difference from Cakemail vs single-account platforms like Mailchimp: opt-outs stay within the Sub-Account scope, not global to the master account.
Frequently Asked Questions
What is the Cakemail FR unsubscribe tag?
The tag is [unsubscribe]. Cakemail replaces it at send time with a signed URL unique per subscriber. Use it inside an anchor: <a href="[unsubscribe]">Unsubscribe</a>.
Do Cakemail FR and Cakemail primary share contact data?
No. Cakemail FR and Cakemail primary run separate account infrastructures with no shared data. Contacts, lists, and suppression must be synced manually via API for multi-country senders using both deployments.
Does Cakemail FR support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. Cakemail injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified under Account > Sender identity.
How does the Sub-Account model handle opt-outs?
Each Sub-Account has its own suppression list scope. Opt-outs stay within the Sub-Account, not global to the master account, letting franchises and agencies segregate compliance per brand or location while sharing infrastructure.
Can I resubscribe a contact who unsubscribed from Cakemail FR?
Not through the API. Cakemail enforces permanent suppression on opt-outs to comply with GDPR and CASL. The contact must re-opt in through a Cakemail signup form, which triggers a fresh double opt-in confirmation email.
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.
