In forceHygieneIn force 1 Feb 2024Verified 2 Aug 2026

Inactive recipients need a documented sunset policy

Q: How long can I keep emailing people who never open or click?

Gmail and Yahoo tell bulk senders to focus on willing, engaged recipients and to reconfirm or consider removing inactive ones. Neither publishes a universal number of days. A sunset window is therefore a documented sender policy—tied to cadence and lifecycle—not a mailbox-provider statute. Mailing multi-year inactive addresses is also how recycled spam traps and complaint spikes form.

Q: In plain English?

Gmail and Yahoo tell bulk senders to focus on people who want the mail. Sunsetting means you pause or reconfirm long-inactive contacts. Pick a window that fits your cadence (a weekly brand and a quarterly brand differ). Write the policy down. Do not invent “Gmail requires 90 days.”

Q: What happens if you do not?

Provider filtering and reputation damage, not a fine for inactivity itself. Combined with trap and complaint signals, inactivity is how programmes quietly die.

How long can I keep emailing people who never open or click?

Global

How email works

In one sentence

Stop regular marketing to people who never engage — or re-ask . There is no magic universal day count from Gmail.

Emailrules interpretation

Gmail and Yahoo tell to focus on people who want the mail. means you pause or reconfirm long-inactive contacts. Pick a window that fits your cadence (a weekly brand and a quarterly brand differ). Write the policy down. Do not invent “Gmail requires 90 days.”

Why it matters. Dead weight on the list drives complaints, traps, and weak . A written is adult list hygiene.

Dotted words open definitions. See how email actually works.

What to do

Your move — not a lecture

This one needs you

No platform does this for you. One concrete move, then you are done.

expose last-open and last-click and can automate suppressions you configure. They will not invent your brand's correct window.

Your part: Choosing the window, the reconfirm path, and whether machine () count as .

What to do first

Define one sentence: "We reconfirm or suppress after N days without a non-machine click or purchase." Put N in writing with the date you chose it. Then count how many profiles exceed N today.

You can skip this if: Your entire list is recent with no multi-year dormant tail.

Who this applies to

Any bulk or lifecycle programme with multi-year lists.

Checklist

01Do not attribute a specific day count to Gmail or Yahoo unless they publish one.
02Prefer clicks, purchases and replies over where inflates opens.
03Run a reconfirm campaign before mass suppression if the revenue risk is real.
04Separate legal (still valid) from (no longer useful).

That’s enough to act. The exact wording, the enforcement record and every primary source sit under Proof & sources, for counsel, bosses, or AI tools that need a citation. Not legal advice.

Proof

Exact position, enforcement, sources

For records and people who will check you. Skip if Monday’s move is already clear.

Source fact

Gmail and Yahoo tell to focus on willing, recipients and to reconfirm or consider removing ones. Neither publishes a universal number of days. A sunset window is therefore a documented sender policy—tied to cadence and lifecycle—not a mailbox-provider statute. Mailing multi-year inactive addresses is also how recycled and complaint spikes form.

What happens if you do not

Provider filtering and damage, not a fine for itself. Combined with trap and complaint signals, inactivity is how programmes quietly die.

Sources

Google, Email sender guidelines
Published 1 Feb 2024Read primary source
Yahoo Sender Best Practices
Published 1 Feb 2024Read primary source

History of this page

2 Aug 2026Added. Explicitly refuses a folklore day count.

Take this with you

GET https://emailrules.today/rules/inactive-recipients-need-a-sunset-policy?format=json

Same URL, same answer, every field including the ones behind the Proof tab. An Accept: application/json header on the plain URL does the same thing. All the endpoints.