Why list decay happens even without new signups

Addresses go bad for reasons that have nothing to do with you:

  • Job changes. When someone leaves a company, their work mailbox is usually disabled and later deleted.
  • Company changes. Acquisitions, rebrands, and shutdowns retire entire domains. A domain may stop publishing MX records, publish an RFC 7505 null MX to declare that it accepts no mail, or lapse entirely.
  • Abandoned personal mailboxes. People move to a new provider or a new address and stop logging in. Major mailbox providers have policies for closing long-inactive accounts.
  • Full or disabled mailboxes. An abandoned inbox can fill up and start rejecting mail long before it is formally closed.

A list sitting untouched still degrades. That is the counterintuitive part: decay is a function of time, not of how often you send.

What decay looks like in your bounce data

Decay surfaces as specific SMTP responses. RFC 3463 defines the enhanced status codes you will see most often:

Code Meaning Typical decay cause
5.1.1 Bad destination mailbox address Employee left, account deleted
5.1.6 Mailbox moved, no forwarding address Address was valid once but no longer accepts mail
5.2.1 Mailbox disabled, not accepting messages Account suspended or deactivated
5.2.2 Mailbox full Inbox abandoned and over quota
5.1.2 Bad destination system address Domain no longer accepts mail

The first three are classic hard bounces. A persistent “mailbox full” response is technically temporary, but when it repeats across several sends it usually means nobody is reading the inbox.

Some decay never bounces at all. An abandoned address that still exists simply stops opening your mail, which drags down engagement. A small share of long-abandoned addresses may eventually be repurposed as recycled spam traps, which is one more reason not to keep mailing addresses that show no signs of life.

Why “verified once” isn’t “verified forever”

A list verified as deliverable today is not guaranteed to stay that way three, six, or twelve months later. The longer the gap between verification and sending, or between sends to an infrequently mailed list, the more decay has accumulated. That is the core argument for periodic re-verification rather than a single cleanup at acquisition.

Decay rate varies by list type and age

A freshly confirmed double opt-in list starts out cleaner and decays more slowly at first than an older list or one built from weaker signup methods. B2B lists of work addresses are more exposed to decay than B2C lists of personal addresses. Purchased or scraped lists are the worst case, since you don’t know how old the data already was.

The practical response to list decay

  1. Re-verify before significant sends. For lists mailed infrequently (quarterly campaigns, seasonal promotions, reactivated dormant segments), run a bulk verification pass right before sending. Decay has had the most time to build up unnoticed there.
  2. Process bounces automatically. Suppress an address after its first hard bounce. Google’s sender guidelines recommend automatically unsubscribing recipients with multiple bounced messages, and Yahoo advises removing invalid recipients promptly.
  3. Sunset unengaged contacts. Both Google and Yahoo recommend periodically reconfirming that recipients still want your mail. Send a re-permission campaign to long-inactive subscribers and remove those who don’t respond.
  4. Watch bounce rate per campaign. A rising rate is the earliest sign that decay is outpacing your hygiene. See what counts as a safe bounce rate for thresholds.
  5. Give subscribers a way to update their address. A preference center lets people move their subscription when they change jobs or providers, rather than letting the old address quietly die.

Where RocketVerifier helps

Bulk email verification lets you re-check a whole list before a send, and pay-as-you-go credits never expire, so you can buy once and re-verify on whatever schedule fits. Unknown results are never charged. When bounces do arrive, the bounce code reference explains what each SMTP response means and whether to suppress the address.