List-Unsubscribe Header: One-Click Unsubscribe Testing with MailSlurp

The List-Unsubscribe header gives mailbox providers a standard place to find the unsubscribe action for marketing and subscribed messages. When it is implemented well, Gmail and other inboxes can show an unsubscribe control near the sender details instead of forcing recipients to hunt through the message body.

MailSlurp helps teams test this before a send. You can deliver a campaign or transactional sample into controlled inboxes, inspect the headers, verify the unsubscribe endpoint, check SPF/DKIM/DMARC alignment, and keep evidence for launch approval.

Quick answer

For Gmail bulk-sender readiness, marketing and subscribed messages should include:

• List-Unsubscribe with an HTTPS unsubscribe URL
• List-Unsubscribe-Post: List-Unsubscribe=One-Click for one-click unsubscribe
• a visible unsubscribe link in the message body
• aligned sender authentication with SPF, DKIM, and DMARC
• accurate headers, sender identity, and message formatting

Google's sender guidelines currently say marketing and subscribed messages must support one-click unsubscribe, and senders over 5,000 messages per day have to meet the stricter bulk-sender requirements.

What the List-Unsubscribe header does

List-Unsubscribe is an email header that points mailbox providers to the unsubscribe action for a mailing list, newsletter, product update, or other subscribed message.

A typical one-click setup includes both headers:

List-Unsubscribe-Post: List-Unsubscribe=One-Click
List-Unsubscribe: <https://example.com/unsubscribe/user-123>

When the recipient uses the native unsubscribe control, the mailbox provider can POST to the unsubscribe URL. Your application should process that request without requiring a login, extra preference screen, or manual email reply.

Why unsubscribe headers affect deliverability

Unsubscribe friction increases complaints. Complaints hurt sender reputation, and sender reputation affects inbox placement.

A clean unsubscribe path helps because it:

• gives recipients a direct opt-out action
• reduces spam complaints from uninterested recipients
• signals that the sender manages subscriptions responsibly
• supports Gmail and Yahoo bulk-sender expectations
• creates a clear QA target before campaign release

The goal is not only compliance. The goal is an email program that recipients can trust and mailbox providers can process reliably.

MailSlurp campaign QA workflow

Use MailSlurp to turn unsubscribe-header checks into a repeatable release step:

1. Send the campaign sample to a controlled MailSlurp inbox.
2. Inspect the raw headers for List-Unsubscribe and List-Unsubscribe-Post.
3. Confirm the unsubscribe URL is HTTPS and points to the right recipient or subscription state.
4. Verify the message body also includes a visible unsubscribe link.
5. Check SPF, DKIM, DMARC, sender identity, and reply-to behavior.
6. Run inbox placement or spam testing before approving the send.

Pair this article with Campaign probe, Campaign quality assurance, and the email header analyzer.

One-click unsubscribe implementation notes

A one-click unsubscribe endpoint should be simple and reliable:

• accept the POST request from the mailbox provider
• identify the recipient or subscription from the URL token
• unsubscribe the recipient from the relevant list
• return a fast success response
• avoid forms, captchas, logins, and preference friction for the one-click action

You can still offer a preference center elsewhere, but the native one-click action should complete the unsubscribe request directly.

Mailto unsubscribe still has a place

Some senders include a mailto: unsubscribe address as a fallback. That can be useful, but Gmail's current bulk-sender guidance calls for one-click unsubscribe on marketing and subscribed mail.

For modern campaign QA, test the HTTPS one-click path first, then verify any mailto: fallback is routed, parsed, and processed correctly.

What to test before sending

Before a campaign or subscribed-message workflow goes live, verify:

• List-Unsubscribe is present and unique enough for the recipient/list
• List-Unsubscribe-Post is present for one-click unsubscribe
• the visible footer unsubscribe link works
• the endpoint returns success and updates subscription state
• SPF, DKIM, and DMARC pass for the sender domain
• the message body, headers, and sender identity are accurate
• the email lands in the expected inbox folder during testing

MailSlurp inboxes make these checks repeatable across previews, approvals, and CI-style campaign gates.

FAQ

What is a List-Unsubscribe header?

It is an email header that tells mailbox providers where to send an unsubscribe request for a mailing list or subscribed message.

What is one-click unsubscribe?

One-click unsubscribe lets a mailbox provider unsubscribe a recipient with a single POST request to the sender's unsubscribe endpoint.

Does every email need List-Unsubscribe?

Transactional messages usually do not use unsubscribe headers. Marketing, newsletter, and subscribed messages should include them and should also include a visible unsubscribe link in the body.

Can MailSlurp test unsubscribe headers?

Yes. Send the message to a MailSlurp inbox, inspect raw headers, verify the unsubscribe URL, check authentication, and keep the message as launch evidence.

Final take

List-Unsubscribe is part of deliverability operations, not just a footer detail. Use MailSlurp to test the header, one-click endpoint, body link, authentication, and inbox behavior before campaigns reach subscribers.