Green Arrow is an on-premise and cloud MTA plus sending platform serving high-volume commercial senders and email service providers who need deep MTA-level control (queue management, per-domain throttling, VirtualMTA routing). The unsubscribe mechanism uses the [-unsublink-] merge tag in the campaign template. RFC 8058 headers are configured at the MTA level through Green Arrow’s list-unsubscribe processing rules. This guide covers the tag, the sender-controlled suppression model, and how to configure RFC 8058 correctly at the MTA layer.
GreenArrow unsubscribe link
| Tag syntax | [-unsublink-] |
| Placement | Manual placement in campaign template body |
| Scope | Per-list plus account-wide blocklist, sender-controlled database |
| Config path | Green Arrow admin > Domain authentication profiles |
| RFC 8058 one-click | Configurable at MTA level via list-unsubscribe processing rules |
How to add the unsubscribe tag in GreenArrow
Place the merge tag exactly as shown below in the email template. GreenArrow replaces it at send time with a signed URL scoped to the recipient and campaign.
[-unsublink-]For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="[-unsublink-]">Unsubscribe from this list</a>Manual placement in campaign template body
Configurable at MTA level via list-unsubscribe processing rules 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.
Green Arrow gives senders full control over the suppression database, unlike SaaS ESPs. This means suppression export, CRM sync, and downstream integration is straightforward, but also means the sender is responsible for correctly configuring MTA-level RFC 8058 header rules per sending domain. Missing configuration means no one-click compliance for that domain.
Testing your GreenArrow unsubscribe link
- Send a test message to a controlled Gmail address you own via the GreenArrow 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 Green Arrow unsubscribe link (step by step)
Green Arrow campaign templates require the unsubscribe merge tag before the send validates. On-premise installations require the unsubscribe web handler configured and reachable from the recipient’s browser.
- Open your campaign template in the Green Arrow admin interface.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
[-unsublink-]. Green Arrow replaces it at send time with a signed URL pointing to the unsubscribe web handler on your Green Arrow installation. - Wrap in an anchor with your preferred label:
<a href="[-unsublink-]">Unsubscribe</a>. - Verify the unsubscribe URL uses HTTPS. Green Arrow config file must have the correct public hostname set for the unsubscribe base URL.
- Send a test to a seed address and click through to confirm the unsubscribe web page loads and removes the address from the target list.
Sender-controlled suppression and lists
Green Arrow gives senders full control over the suppression database, unlike SaaS ESPs where suppression is opaque platform-managed data. Unsubscribes populate a local database that senders query directly for reconciliation with external CRMs. List-level suppression applies by default (the contact remains reachable on other lists), and account-level suppression is enforced through a separate blocklist table that Green Arrow checks before every send. This design suits ESPs reselling Green Arrow infrastructure to their own customers who each need isolated suppression pools.
RFC 8058 at the MTA layer
Green Arrow injects List-Unsubscribe and List-Unsubscribe-Post headers through MTA-level processing rules configured under the sending domain’s authentication profile. SPF, DKIM, and DMARC must be aligned at the MTA before the headers activate. Green Arrow supports one-click unsubscribe POST callbacks that hit the sender’s own web handler, giving deep instrumentation of unsubscribe events without depending on client-side JavaScript or web beacons. This is valuable for high-volume senders needing real-time suppression sync with downstream systems.
VirtualMTA routing and per-domain suppression
Green Arrow’s VirtualMTA feature routes sends through different IP pools based on rules (recipient domain, campaign type, sender reputation tier). Suppression checks happen after VirtualMTA selection, ensuring an unsubscribed contact is blocked regardless of which VirtualMTA the send would have used. Per-domain throttling combines with per-VirtualMTA reputation isolation to give senders granular control over how sending patterns affect deliverability, a level of control that SaaS ESPs deliberately abstract away from customers.
Frequently Asked Questions
What is the Green Arrow unsubscribe merge tag?
The tag is [-unsublink-]. Green Arrow replaces it at send time with a signed URL pointing to the unsubscribe web handler on your Green Arrow installation, unique per recipient and list combination.
Does Green Arrow support one-click unsubscribe for Gmail and Yahoo?
Yes, through MTA-level header injection. Green Arrow adds List-Unsubscribe and List-Unsubscribe-Post headers based on the sending domain’s authentication profile. SPF, DKIM, and DMARC must be aligned. The one-click POST callback hits the sender’s own web handler for direct suppression sync.
Where is Green Arrow suppression data stored?
In the sender’s own database (typically MySQL or PostgreSQL depending on the Green Arrow deployment). Unlike SaaS ESPs, suppression data is fully accessible for direct queries, CRM sync, and export. This is a key differentiator for ESPs reselling Green Arrow infrastructure to their customers.
How does VirtualMTA interact with unsubscribes?
Suppression checks happen after VirtualMTA selection. An unsubscribed contact is blocked regardless of which VirtualMTA the send would have used, ensuring no accidental sends through alternate IP pools bypass opt-outs. VirtualMTA is a routing decision layer, not a suppression bypass.
Is Green Arrow suitable for high-volume senders?
Yes, that is the target market. Green Arrow serves ESPs, high-volume commercial senders, and organizations needing MTA-level control over queue management, per-domain throttling, and IP pool reputation isolation. Low-volume marketers get more value from turnkey SaaS ESPs that abstract MTA operations away.
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.
