phpList is an open-source self-hosted email marketing software popular with nonprofits, associations, and organizations wanting free full-featured newsletter infrastructure on their own servers. The unsubscribe mechanism uses the [UNSUBSCRIBE] placeholder auto-injected into every campaign footer, and phpList supports RFC 8058 header injection when configured in the campaign settings. Suppression is tracked at the list level with account-wide variant available. This guide covers the placeholder, the open-source deployment model, and how to verify the setup end to end.
Phplist Org unsubscribe link
| Tag syntax | [UNSUBSCRIBE] |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with account-wide suppression |
| Config path | Config > Campaign settings > List-Unsubscribe headers |
| RFC 8058 one-click | Manual toggle in phpList campaign settings |
How to add the unsubscribe tag in Phplist Org
Place the merge tag exactly as shown below in the email template. Phplist Org 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
Manual toggle in phpList campaign settings 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.
phpList open-source self-hosted deployment means the sysadmin must enable RFC 8058 header injection in the campaign settings and verify SPF, DKIM, and DMARC alignment on the outbound MTA. Older phpList versions may lack native RFC 8058 support; upgrade to phpList 3.6.14 or newer for baseline one-click compliance. Analogous to Mautic, MailWizz, and Sendy self-hosted patterns where infrastructure configuration is the sender responsibility.
Testing your Phplist Org unsubscribe link
- Send a test message to a controlled Gmail address you own via the Phplist Org 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 phpList unsubscribe link (step by step)
phpList default templates include the unsubscribe placeholder in the footer, but custom HTML templates require the placeholder inserted manually.
- Open your campaign or template in the phpList admin.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the placeholder
[UNSUBSCRIBE]. phpList 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 Config > Campaign settings > List-Unsubscribe headers (phpList 3.6.14 or newer).
- Send a test to a seed address and verify the rendered link routes to the phpList-hosted preference page and the headers are present in the message source.
Open-source self-hosted responsibilities
phpList open-source self-hosted deployment means the sysadmin must enable RFC 8058 header injection in the campaign settings and verify SPF, DKIM, and DMARC alignment on the outbound MTA. Older phpList versions may lack native RFC 8058 support; upgrade to phpList 3.6.14 or newer for baseline one-click compliance. Analogous to Mautic, MailWizz, and Sendy self-hosted patterns where infrastructure configuration is the sender responsibility. Nonprofit and association users who lack sysadmin resources may struggle with the technical baseline required to keep phpList compliant.
RFC 8058 one-click headers via campaign settings
phpList exposes RFC 8058 header injection as a campaign settings toggle. Once enabled on phpList 3.6.14 or newer, the List-Unsubscribe and List-Unsubscribe-Post headers inject on every marketing send from domains authenticated via the outbound MTA. Sysadmins must verify SPF alignment, DKIM signing on the sending domain, and DMARC policy to complete the one-click compliance chain. Older phpList installations lacking the toggle can rely on MTA-side header injection as a fallback.
Nonprofit and association typical use case
phpList typical deployment serves nonprofits, associations, unions, and community organizations wanting free full-featured newsletter infrastructure on their own servers. GDPR compliance depends on sysadmin configuration and campaign practices: double opt-in should be enabled for EU audiences, and consent documentation practices should match GDPR expectations. Preference center customization lets organizations offer granular subscription topics matching typical nonprofit communication categories (fundraising, events, advocacy, member benefits).
Frequently Asked Questions
What is the phpList unsubscribe placeholder?
The placeholder is [UNSUBSCRIBE]. phpList replaces it at send time with a signed URL scoped to the subscriber. Use it inside an anchor: <a href="[UNSUBSCRIBE]">Unsubscribe</a>.
Does phpList support one-click unsubscribe by default?
Only when the campaign settings toggle is enabled and phpList 3.6.14 or newer is installed. Older versions may lack native RFC 8058 support; upgrade or configure MTA-side header injection as a fallback.
Is phpList free?
Yes. phpList is open-source software distributed under the AGPL license. Self-hosting means paying for server and MTA costs but no per-subscriber licensing fees. Hosted phpList services exist for organizations preferring managed hosting.
Is phpList GDPR-compliant?
With proper configuration yes. Enable double opt-in for EU audiences, configure preference center for granular subscription topics, and document consent practices matching GDPR expectations.
How does phpList compare to Mautic or MailWizz?
All three are self-hosted email platforms. phpList emphasizes newsletter simplicity for nonprofits and associations. Mautic focuses on marketing automation and lead scoring. MailWizz targets agencies with multi-account features. Vendor choice depends on feature depth and use case.
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.
