emailDelivery.email is a transactional SMTP relay platform serving developers and SaaS teams with API-based sending, webhook events, and inbound email parsing. The unsubscribe mechanism uses the {{unsubscribe}} merge variable that developers must place manually in the email template body. RFC 8058 headers can be configured through the API metadata parameters when sending marketing-classified messages. Consent is tracked at the recipient level with account-wide suppression list. This guide covers the variable, the API-first architecture, and how to verify the setup end to end.
emaildelivery.com unsubscribe link
| Tag syntax | {{unsubscribe}} |
| Placement | Manual placement in email template body |
| Scope | Recipient-level opt-out with account-wide suppression |
| Config path | API > Send > List-Unsubscribe headers parameter |
| RFC 8058 one-click | Manual via API metadata parameters for marketing sends |
How to add the unsubscribe tag in emaildelivery.com
Place the merge tag exactly as shown below in the email template. emaildelivery.com 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>Manual placement in email template body
Manual via API metadata parameters for marketing sends 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.
emailDelivery.email transactional SMTP relay requires developers to explicitly opt into RFC 8058 header injection per API call for marketing-classified sends. Pure transactional sends (password reset, order confirmation) do not require the headers. Missing the metadata parameter on marketing sends silently falls out of one-click compliance. Configure the send API wrapper to inject the headers by default for any campaign category classified as marketing.
Testing your emaildelivery.com unsubscribe link
- Send a test message to a controlled Gmail address you own via the emaildelivery.com 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 emailDelivery.email unsubscribe link (step by step)
emailDelivery.email is developer-first with no drag-and-drop template editor. Templates are managed via the API or code, with the unsubscribe variable inserted directly in the HTML body.
- Prepare the email template with the placeholder
{{unsubscribe}}in the footer. - Include an anchor:
<a href="{{unsubscribe}}">Unsubscribe</a>. - In the API send call, populate the recipient-scoped unsubscribe URL in the merge variables object.
- For marketing-classified sends, include the
List-UnsubscribeandList-Unsubscribe-Postheaders in the API metadata parameters. - Configure suppression list webhook handlers to update the recipient s consent state on unsubscribe events.
- Send a test to a seed address and verify the rendered link routes to your recipient-scoped unsubscribe handler and updates suppression.
API-first architecture and marketing classification
emailDelivery.email transactional SMTP relay requires developers to explicitly opt into RFC 8058 header injection per API call for marketing-classified sends. Pure transactional sends (password reset, order confirmation) do not require the headers. Missing the metadata parameter on marketing sends silently falls out of one-click compliance. Configure the send API wrapper to inject the headers by default for any campaign category classified as marketing. This is the fundamental architectural pattern shared with SendGrid, Mailgun, Postmark, and SparkPost.
RFC 8058 one-click headers via API metadata
emailDelivery.email exposes RFC 8058 header injection through API metadata parameters rather than a UI toggle. Developers building marketing send flows must include the List-Unsubscribe header (mailto and https URLs) and the List-Unsubscribe-Post header (One-Click) in every marketing-classified API call. SPF and DKIM alignment on the sender domain is prerequisite: unauthenticated sending domains fall out of one-click compliance regardless of header presence.
Webhook events and suppression sync
emailDelivery.email webhook events fire on unsubscribe, bounce, spam complaint, and delivery notifications. Developers should subscribe to the unsubscribe webhook to update the recipient s consent state in the application database and prevent further marketing sends. Missing this integration leaves the account-wide suppression list as the sole enforcement point, which can create inconsistencies if the application has its own marketing send logic outside emailDelivery.email s scope.
Frequently Asked Questions
What is the emailDelivery.email unsubscribe variable?
The merge variable is {{unsubscribe}}. Populate the recipient-scoped unsubscribe URL in the API send call merge variables object. Use it inside an anchor: <a href="{{unsubscribe}}">Unsubscribe</a>.
Do transactional sends need RFC 8058 headers?
No. Pure transactional sends (password reset, order confirmation) do not require RFC 8058 headers. Only marketing-classified sends need the headers, and developers must opt in per API call.
Does emailDelivery.email support one-click unsubscribe?
Yes via API metadata. Include the List-Unsubscribe and List-Unsubscribe-Post headers in the API metadata parameters on marketing-classified sends. SPF and DKIM alignment on the sender domain is prerequisite.
How do I sync emailDelivery.email suppression to my app?
Subscribe to the unsubscribe webhook. On unsubscribe events, update the recipient s consent state in your application database. Missing this integration leaves the account-wide suppression list as the sole enforcement point.
How does emailDelivery.email compare to SendGrid?
Both are transactional SMTP relays with API-based sending. Feature differences include webhook event granularity, inbound parsing, pricing model, and template management. Deliverability comparisons depend on IP reputation and sender authentication rather than platform choice.
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.
