SendyBay is a hosted Sendy service provider, offering the self-hosted Sendy Amazon SES-based email marketing software as a managed SaaS. The unsubscribe mechanism uses the [unsubscribe] merge tag auto-injected into every campaign footer, and SendyBay emits RFC 8058 headers when the underlying Sendy configuration and Amazon SES Configuration Set support them. Suppression is tracked at the list level. This guide covers the tag, the hosted Sendy model, and how to verify the setup end to end.
sendybay unsubscribe link
| Tag syntax | [unsubscribe] |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with SES-based suppression |
| Config path | Sendy Admin > Brands > Sender identity |
| RFC 8058 one-click | Via Sendy plus Amazon SES Configuration Set |
How to add the unsubscribe tag in sendybay
Place the merge tag exactly as shown below in the email template. sendybay 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
Via Sendy plus Amazon SES Configuration Set 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.
SendyBay is a managed Sendy hosting service running on Amazon SES infrastructure. RFC 8058 compliance depends on both the Sendy version (recent Sendy 6+ supports List-Unsubscribe headers) and the underlying SES Configuration Set. SendyBay handles server management, but Amazon SES account authentication (SPF, DKIM, DMARC) remains the customer responsibility. Analogous to MailBluster and Blastable SES-based patterns.
Testing your sendybay unsubscribe link
- Send a test message to a controlled Gmail address you own via the sendybay 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 SendyBay unsubscribe link (step by step)
SendyBay 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 SendyBay Sendy admin.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
[unsubscribe]. Sendy replaces it at send time with a signed URL scoped to the subscriber. - Wrap it in an anchor:
<a href="[unsubscribe]">Unsubscribe</a>. - Enable RFC 8058 header injection under Sendy Admin > Brands > Sender identity (Sendy 6+ requirement).
- Send a test to a seed address and verify the rendered link routes to the Sendy-hosted preference page and the headers are present in the message source.
Managed Sendy hosting model
SendyBay is a managed Sendy hosting service running on Amazon SES infrastructure. RFC 8058 compliance depends on both the Sendy version (recent Sendy 6+ supports List-Unsubscribe headers) and the underlying SES Configuration Set. SendyBay handles server management, but Amazon SES account authentication (SPF, DKIM, DMARC) remains the customer responsibility. Analogous to MailBluster and Blastable SES-based patterns where the platform reduces sysadmin burden but SES account ownership stays with the sender.
RFC 8058 via Sendy plus Amazon SES
SendyBay RFC 8058 compliance requires Sendy 6+ with List-Unsubscribe headers enabled, plus Amazon SES Configuration Set attached to the sending identity. SES Configuration Sets support header injection at the MTA layer. Verify SPF, DKIM, and DMARC records on the sending domain match Amazon SES verification. Custom TLD sends require the sending domain to be verified in the customer s SES account, not just the SendyBay parent.
Cost model versus self-hosted Sendy
SendyBay cost model bundles Sendy license, server hosting, and updates for a recurring subscription fee. Self-hosted Sendy is one-time license plus DIY server management. Customers valuing SES cost per email while offloading sysadmin work choose SendyBay. Customers wanting maximum cost control and having sysadmin capacity choose self-hosted Sendy directly. Cost comparison should include SES sending fees separately since SES billing routes to the customer AWS account.
Frequently Asked Questions
What is the SendyBay unsubscribe tag?
The merge tag is [unsubscribe]. Sendy replaces it at send time with a signed URL scoped to the subscriber. Use it inside an anchor: <a href="[unsubscribe]">Unsubscribe</a>.
Is SendyBay the same as Sendy?
SendyBay is a managed Sendy hosting service. The underlying software is Sendy running on Amazon SES infrastructure. SendyBay handles server management; SES account authentication stays with the customer.
Does SendyBay support one-click unsubscribe for Gmail and Yahoo?
Yes when Sendy 6+ is running with List-Unsubscribe headers enabled and Amazon SES Configuration Set attached. Verify SPF, DKIM, and DMARC on the sending domain match SES verification.
Who handles Amazon SES billing on SendyBay?
The customer AWS account. SendyBay hosts the Sendy application but sends through the customer s own SES account. Cost comparison should include SES sending fees separately from SendyBay subscription.
How does SendyBay compare to MailBluster or Blastable?
All three are SES-based email platforms. SendyBay runs the Sendy application. MailBluster and Blastable are proprietary SaaS built on SES. Vendor choice depends on feature preferences and Sendy familiarity.
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.
