Sarbacane is a French email marketing platform serving French and European SMBs and mid-market with drag-and-drop editor, SMS integration, and RGPD-first defaults. The unsubscribe mechanism uses the [DESABONNEMENT] merge tag auto-injected into every campaign footer, and Sarbacane emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the contact level with French RGPD/CNIL enforcement. This guide covers the tag, the French RGPD model, and how to verify the setup end to end.
Sarbacane unsubscribe link
| Tag syntax | [DESABONNEMENT] |
| Placement | Auto-embedded in every campaign footer |
| Scope | Contact-level opt-out with French CNIL enforcement |
| Config path | Parametres > Profils expediteur > Pied de page |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Sarbacane
Place the merge tag exactly as shown below in the email template. Sarbacane replaces it at send time with a signed URL scoped to the recipient and campaign.
[DESABONNEMENT]For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="[DESABONNEMENT]">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.
Sarbacane French RGPD compliance combined with CNIL enforcement quarantines imported contact lists without documented consent. French senders migrating from other ESPs must provide RGPD documentation for each contact. Analogous to Ecomail-fr, Courrielleur, and Mailjet French regulatory-first patterns. The [DESABONNEMENT] tag is French-native (unsubscribe in French) and templates ship with French-first UX for the domestic market.
Testing your Sarbacane unsubscribe link
- Send a test message to a controlled Gmail address you own via the Sarbacane 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 Sarbacane unsubscribe link (step by step)
Sarbacane 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 Sarbacane editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
[DESABONNEMENT]. Sarbacane replaces it at send time with a signed URL scoped to the contact. - Wrap it in an anchor:
<a href="[DESABONNEMENT]">Se desabonner</a>. - Configure the sender identity under Parametres > Profils expediteur > Pied de page.
- Send a test to a seed address and verify the rendered link routes to the Sarbacane-hosted preference page.
French RGPD-first defaults
Sarbacane French RGPD compliance combined with CNIL enforcement quarantines imported contact lists without documented consent. French senders migrating from other ESPs must provide RGPD documentation for each contact. Analogous to Ecomail-fr, Courrielleur, and Mailjet French regulatory-first patterns. The [DESABONNEMENT] tag is French-native (unsubscribe in French) and templates ship with French-first UX for the domestic market. Sarbacane also supports English, Spanish, and Italian templates for European multi-market senders.
RFC 8058 one-click headers
Sarbacane 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 Parametres > Profils expediteur. SPF and DKIM records must be verified. French RGPD requires documented consent for imported lists and Sarbacane suppression files honor cross-campaign compliance.
SMS integration and French domestic market
Sarbacane SMS integration lets French senders coordinate email and SMS campaigns from a unified contact database. French SMS opt-out expectations under CNIL guidance are stricter than email since SMS is considered more intrusive. Configure SMS opt-out enforcement to honor STOP keyword replies immediately per French SMS best practices. Domestic focus on French SMBs and mid-market with French-language support and RGPD-native workflows differentiates Sarbacane from US-founded ESPs serving French customers as secondary market.
Frequently Asked Questions
What is the Sarbacane unsubscribe tag?
The merge tag is [DESABONNEMENT]. Sarbacane replaces it at send time with a signed URL scoped to the contact. Use it inside an anchor: <a href="[DESABONNEMENT]">Se desabonner</a>.
Sarbacane est-il conforme au RGPD?
Oui, par defaut. Sarbacane applique les exigences RGPD et CNIL: consentement documente pour les listes importees, suppression cross-campagne, et pied de page francophone natif. Les listes sans consentement documente sont mises en quarantaine.
Does Sarbacane support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. Sarbacane injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified under Parametres > Profils expediteur.
Est-ce que le STOP SMS est traite automatiquement?
Oui. Sarbacane honore les reponses STOP immediatement selon les bonnes pratiques SMS francaises sous la CNIL. Le contact est supprime des envois SMS futurs mais peut continuer a recevoir des emails sauf opt-out email distinct.
How does Sarbacane compare to Brevo or Mailjet for French senders?
All three are French-founded. Sarbacane emphasizes French SMB domestic focus. Brevo (ex-Sendinblue) is broader European with transactional API. Mailjet is French with focus on developer API. Vendor choice depends on API needs vs interface preference.
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.
