The specific email that causes this

It is almost always the birthday email. An agent buys or exports a few hundred old leads, loads them into a CRM, switches on the automated birthday campaign, and a branded card goes out to someone who filled in a home-value form in 2023 and has not heard from that agent since.

Put yourself on the other end. You get a graphic-heavy email wishing you a happy birthday from a name you do not recognize, at a brokerage you do not recognize, for a house you are not selling. You do not think what a thoughtful agent. You think how did this person get my birthday — and you hit the button that makes it stop.

That button is Report spam, not Unsubscribe. This is the part agents miss. Recipients do not read the difference between the two, and the mailbox provider treats them very differently.

The math is brutal on a small list

Agents assume complaint thresholds are a big-sender problem. The percentages say otherwise, and small lists actually make it worse.

Google's sender guidelines tell senders to "keep spam rates reported in Postmaster Tools below 0.10%" and to "avoid ever reaching a spam rate of 0.30% or higher." Yahoo applies a comparable bar.

Run that against a realistic agent database:

  • 400 recipients. One complaint = 0.25%. You are already past Google's recommended level on a single click.
  • Two complaints = 0.50%, which is well past the line where mail starts getting rejected or junked outright.
  • A blast to a cold three-year-old list does not generate one complaint. It generates a handful, on the first send, within an hour.

A large sender has ten thousand engaged subscribers absorbing a few complaints. You do not. Every complaint on a small list is a large percentage, which is why "it's only a few hundred people, what's the harm" is exactly backwards.

Dead addresses are worse than no addresses

There is a second mechanism working against an old list, and it is quieter.

When someone abandons an email address, the provider eventually stops bouncing mail to it and turns it into a recycled spam trap — an address whose only purpose is to identify senders who are mailing a list they have not maintained. Industry guidance generally puts the dormancy period before recycling at a year or more.

A lead list from three years ago is, by definition, full of addresses nobody has opened in three years. You cannot tell which ones from the outside. Hitting a trap is not a soft signal — it is a direct statement to the filter that you are mailing people who never asked and never engaged.

What actually gets damaged (this is the important part)

Agents think the downside of a bad send is a bad open rate. The real downside is that reputation attaches to your sending domain, and your sending domain is usually the domain your business runs on.

Google states it plainly: "Over time, user spam reports can lower your domain's reputation." And on recovery: "It can take time for improvements in spam rate to reflect positively on spam classification." Damage is fast and repair is slow — that asymmetry is the whole risk.

Now think about what else leaves that domain:

  • An offer to a listing agent on a Friday afternoon.
  • A signed addendum to the title company.
  • Documents to a lender against a financing deadline.
  • The first reply to a real inquiry from a real seller.

None of those are marketing. All of them are filtered by the same reputation you just spent on a birthday card. An agent who has to phone a title officer and say "check your junk folder" has already paid more than the campaign could ever have returned.

The honest version of the sender rules

You will see agent-marketing content claiming the 2024 Gmail and Yahoo rules and Microsoft's 2025 Outlook requirements apply to you. Mostly, they do not, and we are not going to pretend otherwise.

Those bulk sender requirements are scoped to domains sending roughly 5,000 or more messages a day to that provider's users. A solo agent with a 900-person database is nowhere near that, so the mandatory authentication regime is not what is filtering your mail.

What does apply to everyone, at every volume:

  • Complaint rate. A percentage does not care how small your list is.
  • Engagement signals. Deleted-without-reading, never-opened, and no-reply all feed placement decisions.
  • Consent. Google's guidance is blunt — "Don't send messages to people who didn't sign up to get messages from you." A portal lead who requested a home value estimate did not sign up for your newsletter.

Worth doing anyway, because it is cheap and it helps at any volume: set up SPF, DKIM, and DMARC on your domain, and send marketing from a subdomain (news.yourdomain.com) so a bad campaign cannot drag your transaction email down with it.

What to do with the list you already have

You have the addresses. Deleting them feels wasteful. Here is the sequence that does not cost you your domain.

  1. Sort by last real interaction, not by date acquired. Someone who replied to you eight months ago is a different asset from someone who has never responded to anything.
  2. For anyone genuinely warm, write one plain-text email, one at a time, from you. No template, no header graphic, no unsubscribe footer — because it is not marketing. Reference the actual thing: the house they asked about, the neighborhood, when you met. This is the single most effective thing in this post and it does not scale, which is why almost nobody does it.
  3. For the never-engaged, send nothing. Not a re-permission campaign, not a "we miss you" email — those are still blasts to people who do not know you. If you want them back, use a channel where being forgotten is not punished: a call, a handwritten note, a postcard, a genuinely useful lead magnet they choose to opt into.
  4. Sunset dormant addresses on a rule. No opens in 6-12 months, out of the sending list. You are not losing a customer; you are removing an address that can only hurt you.
  5. Then earn the list forward. An email list you actually built — people who asked to hear from you and hear from you consistently — is one of the few marketing assets you genuinely own. It is also the one most easily destroyed by a single lazy send.

Why this keeps happening

The underlying mistake is not really about email. It is treating a contact record as a relationship.

A name in a CRM feels like an asset, so "stay top of mind" gets interpreted as "send something." But being remembered is not produced by frequency — it is produced by having been relevant to someone at least once. Sending a birthday card to a stranger is not staying top of mind; it is announcing that you have a database.

This is the same trap as buying portal leads and calling them a pipeline: the record exists, so it feels like progress, while the actual asset — someone who knows who you are and would take your call — was never built. If you want the version of this that compounds instead of decays, the free DIY playbook is the order we run it in.