GroupMail (by Infacta) is a Windows desktop bulk email software popular with small businesses, associations, and non-profits who prefer local sending over SaaS platforms. The unsubscribe mechanism uses the %%UNSUBSCRIBE_LINK%% merge field in the message template, replaced at send time with a signed URL scoped to the recipient list entry. Since GroupMail sends through user-configured SMTP relays (Gmail, custom SMTP, dedicated relay), RFC 8058 headers depend on the underlying relay configuration and require manual header injection at the SMTP relay level. This guide covers the tag, the local database model, and how to verify the setup end to end.
GroupMail unsubscribe link
| Tag syntax | %%UNSUBSCRIBE_LINK%% |
| Placement | Manual placement in message template |
| Scope | Per-list opt-out in local database |
| Config path | GroupMail > Tools > Options > Sending profiles |
| RFC 8058 one-click | Requires manual header injection at the SMTP relay level |
How to add the unsubscribe tag in GroupMail
Place the merge tag exactly as shown below in the email template. GroupMail replaces it at send time with a signed URL scoped to the recipient and campaign.
%%UNSUBSCRIBE_LINK%%For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="%%UNSUBSCRIBE_LINK%%">Unsubscribe from this list</a>Manual placement in message template
Requires manual header injection at the SMTP relay level 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.
GroupMail is desktop software, so unsubscribes are stored in the local database on the sender machine. Unsubscribes are not synced across multiple installations or team members using GroupMail on different machines. For team environments, export the suppression list weekly and merge across installations, or migrate to a SaaS ESP with centralized suppression.
Testing your GroupMail unsubscribe link
- Send a test message to a controlled Gmail address you own via the GroupMail 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 GroupMail unsubscribe link (step by step)
GroupMail message templates require manual placement of the unsubscribe merge field since the platform serves local desktop senders building custom HTML templates.
- Open your message template in the GroupMail Windows client.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge field
%%UNSUBSCRIBE_LINK%%. GroupMail replaces it at send time with a signed URL scoped to the recipient list entry. - Wrap in an anchor:
<a href="%%UNSUBSCRIBE_LINK%%">Unsubscribe</a>. - Configure the SMTP relay under Tools > Options > Sending profiles. RFC 8058 header injection requires the relay to be configured for List-Unsubscribe headers.
- Send a test to a seed address and verify the rendered link routes to the GroupMail-hosted unsubscribe confirmation page.
Local database and multi-installation challenges
GroupMail is desktop software, so unsubscribes are stored in the local database on the sender machine. Unsubscribes are not synced across multiple installations or team members using GroupMail on different machines. For team environments, export the suppression list weekly and merge across installations, or migrate to a SaaS ESP with centralized suppression. Cloud sync options are available in the GroupMail Business tier via the Infacta Cloud sync service, which is recommended for teams of 3+ users to avoid suppression drift.
RFC 8058 and SMTP relay configuration
GroupMail does not inject RFC 8058 headers directly since it hands off to the configured SMTP relay for delivery. To satisfy the Google and Yahoo bulk-sender requirements, the underlying SMTP relay must be configured for List-Unsubscribe headers. For Gmail SMTP relay (up to 2000 sends per day), Google injects headers automatically for authenticated Workspace domains. For dedicated relays like Amazon SES or SendGrid, configure the Configuration Set to inject List-Unsubscribe headers at the relay level. GroupMail is not suited to high-volume senders requiring one-click compliance out of the box.
Bounce handling and suppression sync
GroupMail bounce handling relies on the SMTP relay bounce processing. Hard bounces are added to the local suppression list when the bounce feedback is processed by the GroupMail Bounce Manager. Soft bounces are retried up to configurable thresholds before being classified as hard bounces. For teams, the local bounce database means bounce state is not shared across installations, another reason multi-user teams should migrate to a SaaS ESP or enable Infacta Cloud sync.
Frequently Asked Questions
What is the GroupMail unsubscribe tag?
The merge field is %%UNSUBSCRIBE_LINK%%. GroupMail replaces it at send time with a signed URL scoped to the recipient list entry. Use it inside an anchor: <a href="%%UNSUBSCRIBE_LINK%%">Unsubscribe</a>.
Where is GroupMail unsubscribe data stored?
In the local database on the sender machine. Unsubscribes are not synced across multiple installations by default. Enable Infacta Cloud sync (available in the Business tier) to centralize suppression across a team.
Does GroupMail support one-click unsubscribe for Gmail and Yahoo?
Only if the configured SMTP relay injects the List-Unsubscribe headers. GroupMail does not inject headers directly since it hands off to the relay. Gmail SMTP relay includes headers automatically for authenticated Workspace domains; dedicated relays like Amazon SES or SendGrid require Configuration Set setup.
Is GroupMail suitable for high-volume senders?
Not typically. GroupMail suits small-volume senders (under 5,000 emails per day) using local desktop workflows. High-volume senders benefit from SaaS ESPs with centralized suppression, dedicated IPs, and turnkey RFC 8058 compliance without SMTP relay configuration.
Can I migrate a GroupMail suppression list to a SaaS ESP?
Yes. Export the suppression list from GroupMail as CSV under Tools > Export > Suppression list, then import into the destination ESP suppression / blocklist. This preserves opt-out history during migration and prevents accidentally re-emailing unsubscribed contacts.
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.
