Skip to content
RRAECHLY

Deliverability glossary · Updated 2026-08-10

List-Unsubscribe

List-Unsubscribe is an email header giving mailbox providers a machine-readable way to opt someone out. It renders as the native unsubscribe link Gmail shows next to the sender name.

The header can carry a `mailto:` address, an HTTPS URL, or both. Mailbox providers use it to render their own unsubscribe control in the interface, which is a far more prominent and trusted affordance than a link buried in your footer.

Counter-intuitively, making unsubscribing easy protects you. The alternative action available to an irritated recipient is the spam button, and a spam complaint damages your sending reputation in a way an unsubscribe does not. Every opt-out taken through the header is a complaint you did not receive.

Since February 2024, Gmail and Yahoo have required List-Unsubscribe for bulk senders, together with one-click support and a complaint rate kept under 0.3%. It moved from best practice to a delivery requirement in a single policy change.

The header must be present on the message itself, which means the sending system needs control over raw MIME rather than only a templating layer above it.

How Raechly handles it

Every message is assembled as raw MIME so List-Unsubscribe, Precedence: bulk and a stable Message-ID can be set per send. That control is the reason the SES integration builds MIME by hand instead of using a simpler send API.

Related terms

Back to the full deliverability glossary, or read how these pieces fit together in how Raechly protects deliverability.

Deliverability you can check, not take on trust.

Raechly reports what it can prove: verified DKIM, verified reply capture, and the verbatim error on every failed send.