Google and Yahoo one-click unsubscribe requirements

Google and Yahoo both set one-click unsubscribe expectations for bulk senders, but they do not use the same threshold, enforcement timing, or processing deadline. Google applies its rule to senders of more than 5,000 messages per day to personal Gmail accounts from 1 February 2024. Yahoo does not publish a numeric bulk-sender threshold, began List-Unsubscribe enforcement in June 2024, and requires unsubscribes within two days.

Who is affected?

Google and Yahoo assess their own recipient traffic and sender requirements. One-click unsubscribe is part of wider mailbox-provider expectations that can affect deliverability, alongside authentication and complaint handling. See the deliverability learning center for the surrounding operational context.

Google: senders above 5,000 messages per day to personal Gmail accounts

Google's email sender guidelines require senders of more than 5,000 messages per day to personal Gmail accounts to support one-click unsubscribe. The guideline applies to mail sent to personal Gmail accounts, not Google Workspace accounts.

That qualifier matters for B2B programs. A sender that mails only Google Workspace recipients is outside this specific Google rule, even though its mail can still be subject to other authentication, spam, and recipient-policy checks.

Google's published threshold is a daily message volume, not a count of subscribers, campaigns, or domains.

Yahoo: significant-volume bulk senders, without a published number

Yahoo uses a different definition. Its sender FAQ states: "A 'bulk' sender is classified as an email sender sending a significant volume of mail. We will not specify a volume threshold."

Do not apply Google's 5,000-message figure to Yahoo. Yahoo's rule may affect senders that cannot classify themselves from a published volume cutoff, so marketing teams should treat the requirement as an operational standard for meaningful Yahoo-bound campaign volume.

Yahoo also limits the one-click requirement by message type. Its FAQ states: "One-click unsubscribe is only required for promotional/marketing messages. The requirement does not apply to transactional messages." Google’s guidelines read for this article do not document that same message-type carve-out, so it should not be treated as a shared rule.

What are the requirements?

Google requires RFC 8058 one-click unsubscribe above its threshold

Google says qualifying bulk senders must support one-click unsubscribe with the List-Unsubscribe and List-Unsubscribe-Post headers defined in RFC 8058.

List-Unsubscribe: <https://unsubscribe.yourdomain.com/list/opaque-token>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

RFC 8058 is an IETF Standards Track RFC published in January 2017. Section 4 requires both headers to be covered by the DKIM signature's h= tag. The standard describes the protocol mechanism, while Google decides which senders must use it.

For the header construction, DKIM coverage, and endpoint behavior, use the focused RFC 8058 one-click unsubscribe guide. A published record or platform setting alone does not prove that delivered production mail carries the required headers.

Yahoo requires a functioning list-unsubscribe header for covered mail

Yahoo's sender best practices say bulk senders should "Implement a functioning list-unsubscribe header, which supports one-click unsubscribe for marketing and subscribed messages". The same page says the POST method in RFC 8058 is "highly recommended."

Yahoo's sender FAQ describes the requirement more directly: "You must implement the list-unsubscribe header (preferably according to RFC 8058) in order to meet the requirement for one-click unsubscribe."

Those statements should be read together. Yahoo requires a functioning list-unsubscribe header for the covered message types, and identifies RFC 8058 as the preferred one-click method. Do not turn Yahoo's "highly recommended" wording for the RFC 8058 POST method into a universal Yahoo mandate.

Yahoo requires unsubscribes within two days

Yahoo's best-practices page requires senders to "Honor unsubscribes within 2 days." Its FAQ confirms: "If the unsubscribe is not honored in 2 days, then it would not meet the requirement."

This is a Yahoo-specific processing deadline. Google's sender-guidelines page states no processing deadline, so two days is not a shared Google and Yahoo requirement.

The deadline concerns the durable suppression outcome. An HTTP response from an unsubscribe endpoint does not establish that all relevant campaign systems, ESPs, and production sending paths will stop sending the covered mail.

Yahoo may route noncompliant mail to spam or reject it

Yahoo's FAQ states: "If you do not meet the requirements, your mail may be sent to the spam folder or rejected. If mail is rejected, we will return a specific error code with information about the rejection."

"May" is important. Yahoo does not say every noncompliant message will be rejected. The public documentation confirms that a specific error code can accompany a rejection, but it does not enumerate the exact strings.

Yahoo also requires bulk senders to keep spam complaint rates below 0.3%, which is separate from one-click unsubscribe. For the wider provider checklist, see Yahoo bulk sender requirements.

When does the requirement take effect?

Google's sender guidelines state that the requirements for senders of more than 5,000 messages per day took effect on 1 February 2024. The applicable scope is personal Gmail accounts.

Yahoo's staged timeline is different. Its FAQ states: "Enforcement will begin in February 2024, and we will continue to gradually roll out enforcement as we monitor compliance metrics. Note: Enforcement of the List-Unsubscribe policy will begin in June 2024."

The February 2024 Yahoo date refers to enforcement beginning for its broader requirements. June 2024 is the source-backed enforcement date for Yahoo's List-Unsubscribe policy specifically. Do not collapse those dates into a single shared deadline.

How do I implement the requirement?

1. Classify the traffic by recipient and message type

Measure daily volume to personal Gmail accounts separately from Google Workspace recipients. For Yahoo, identify marketing and subscribed mail separately from transactional mail.

Keep this classification tied to the actual production sending path. A campaign tool's audience estimate may not match final recipient routing or send volume.

2. Configure the list-unsubscribe mechanism in the sending platform

Configure the sender to include a functioning list-unsubscribe header for the covered messages. For Google-qualifying bulk mail, configure the RFC 8058 one-click headers.

The header values, recipient token design, and POST endpoint are implementation details covered in the dedicated one-click unsubscribe requirements guide. Use values generated for your own sending environment. Do not copy another tenant's unsubscribe URLs or identifiers.

3. Ensure DKIM signs the relevant RFC 8058 headers

For RFC 8058 use, send a controlled message and inspect its actual DKIM signature. RFC 8058 requires the DKIM h= tag to cover both List-Unsubscribe and List-Unsubscribe-Post.

A vendor screen that says DKIM is enabled is not evidence that the delivered message signed these fields.

4. Connect the unsubscribe action to the production suppression state

Test an unsubscribe with a safe test recipient. Confirm that the action updates the system that governs every relevant campaign sender, not only a web preference center or one application database.

For Yahoo-covered promotional or marketing mail, verify that the recipient is suppressed within two days. Preserve only the evidence needed for troubleshooting, and avoid storing full recipient-specific unsubscribe URLs in routine logs.

A redirect, login requirement, or browser-only confirmation flow can break the RFC 8058 one-click transaction. Test the same HTTPS POST behavior that a mailbox provider can use.

How do I validate compliance?

Validate one-click unsubscribe at four layers.

• DNS: Confirm the domain's DMARC and DKIM records resolve through the authoritative DNS service and a public resolver. This confirms published DNS, not delivered-message behavior.
• Vendor: Check the sending platform's current authentication and unsubscribe configuration. A green platform status does not prove the production path adds the headers.
• Message: Send a real test message through the exact production path and inspect its raw headers. Confirm the required list-unsubscribe headers are present and, for RFC 8058, covered by a valid DKIM signature.
• DMARC and delivery: Review aggregate-report data after mail has been sent. For Yahoo, use Yahoo Sender Hub to review its aggregated domain delivery statistics where available.

Check the wider sender posture behind the unsubscribe requirement

One-click unsubscribe is only one provider expectation. Use the email security score to inspect the domain's public authentication posture before comparing it with delivered-message headers and the sender platform's settings.

The score cannot verify a list-unsubscribe header, test an unsubscribe endpoint, monitor future sender changes, or prove how Gmail or Yahoo will place an individual message.