Deliverability is a permission problem before it is a technical one

Ask why email lands in spam and you will get a technical answer: authentication records, sending domain, IP warm-up, HTML weight. All of that is real, and DearReach handles most of it for you. But it is the smaller half of the problem.

Authentication proves the mail is genuinely from you. It does not prove anyone wanted it.

What mailbox providers are actually measuring

Gmail, Outlook, and the rest are not grading your CSS. They are watching how humans respond to you over time:

• Do people open, reply, and click, or does the message sit unread?
• Do they move you out of spam, or into it?
• Do they hit the complaint button?
• Are you sending to addresses that no longer exist?

A message can pass every authentication check and still get filed away, because the signal that matters is whether your last few hundred recipients acted like people who asked to hear from you.

The failure modes are almost always consent-shaped

In practice, the mail that struggles usually comes from one of these:

Bought or scraped lists. Nobody on them opted in. Complaint rates spike immediately, and the damage attaches to your domain, not to the list.

Old lists mailed after a long silence. Addresses have been abandoned or turned into spam traps. Two years of silence is not a pause, it is a lapsed relationship.

Consent by proxy. Someone downloaded a PDF, or handed you a business card, or attended a webinar. That is contact information, not permission to publish to them weekly.

One list for everything. People signed up for one thing and receive another. The unsubscribe is honest feedback, and the complaint is the same feedback delivered louder.

None of those are fixed by a DNS record.

What good permission looks like

The version that works is unglamorous:

• Ask clearly, and say what you will send and roughly how often.
• Use confirmed opt-in when the source is at all uncertain.
• Let people choose topics rather than making it all or nothing.
• Make unsubscribing easy and instant. A quiet exit is far cheaper than a complaint.
• Send often enough that people remember signing up.

That last point catches good writers out. If you mail twice a year, every send feels like it came from a stranger, and strangers get reported.

Where the tool should help

Permission is your decision. What software can do is make the decision stick and stop you undoing it by accident.

DearReach enforces suppression at two points, once when the audience is built and again immediately before each message goes to the provider, so somebody who unsubscribed between those two moments still does not receive it. Bounces and complaints feed straight back into suppression. If the numbers on a send turn bad, delivery pauses rather than pushing on and burning your domain.

You still have to earn the permission. The tool’s job is to make sure it is never quietly spent.

More on the practical side in Deliverability best practices and Permission and suppression.