Tag: Enforcement

A giant company can send ten million messages and remain visible.

A tiny sender can get blocked after a much smaller campaign.

That observation is real.

The explanation is not automatically the big company gets special treatment.

To establish unequal treatment, the traffic has to be comparable first.

Gmail currently defines a bulk sender as one that sends roughly 5,000 or more messages per day to personal Gmail accounts. Once a domain crosses that threshold, Gmail permanently treats it as a bulk sender and applies additional requirements such as SPF and DKIM, DMARC, alignment, one-click unsubscribe for promotional messages, and low complaint rates. See Gmail’s sender guidelines FAQ.

That is explicit size-based treatment.

It is stricter, not looser.

Raw volume is not enough

Suppose a national retailer sends five million promotional messages from a domain with years of authenticated history, clear unsubscribe controls, and a 0.05% complaint rate.

A tiny unknown sender sends 20,000 cold pitches from a fresh domain and gets a 2% complaint rate.

The large sender generated more complaints in absolute numbers.

The small sender generated a much larger proportion of complaints.

Those campaigns are not equivalent evidence.

A serious comparison needs to control for at least:

complaint rate as well as complaint count,
whether recipients subscribed or had a prior relationship,
whether the content was transactional or promotional,
authentication and domain reputation,
bounce and invalid-address rates,
unsubscribe behavior,
sending history,
and the exact enforcement action being compared.

Otherwise size becomes a convenient explanation for differences caused by something else.

Reputation can look like privilege

Established senders often have technical advantages.

They may use dedicated deliverability teams, mature suppression lists, strong authentication, predictable sending patterns, and direct relationships with major mailbox providers.

Those advantages can improve delivery.

They can also make the system feel unfair to a smaller operator who lacks the same infrastructure.

That still does not prove comparable abusive traffic was treated differently because of corporate status.

Proof would require cases where similarly unwanted traffic, measured the same way, triggered materially different outcomes after accounting for the operational variables.

The question is worth asking carefully

Large organizations do have resources smaller senders do not.

They can hire experts, negotiate with vendors, monitor Postmaster dashboards, maintain dedicated IP space, and fix reputation problems faster.

That creates real asymmetry.

But asymmetry of capability is not the same claim as selective tolerance of equivalent abuse.

DIT-300 closes Spam Empires on that distinction.

The industrial internet absolutely treats senders differently according to scale, history, infrastructure, and reputation.

If the accusation is that a major advertiser gets away with behavior that would destroy a small sender, the evidence has to compare behavior rather than logos.

Otherwise the conclusion arrives before the experiment.

One thousand spam complaints sounds catastrophic.

It might be.

It might also represent one-tenth of one percent of a million delivered messages.

Scale makes raw complaint counts surprisingly easy to misuse.

Gmail currently tells senders to keep user-reported spam rates below 0.1% and to prevent them from reaching 0.3% or higher. For bulk senders, rates at or above 0.3% can make them ineligible for delivery mitigation until the rate remains below that level for seven consecutive days. See Gmail’s sender guidelines FAQ.

Yahoo likewise tells senders to keep complaint rates below 0.3%. See Yahoo Sender Hub best practices.

These systems use rates for a reason.

Counts punish size; rates can hide volume

Imagine two senders.

Sender A delivers 1,000 messages. One recipient reports spam.

Complaint rate: 0.1%.

Sender B delivers 1,000,000 messages. One thousand recipients report spam.

Complaint rate: also 0.1%.

The rate says the same fraction of recipients objected.

The count says Sender B created one thousand times as many individual complaints.

Neither measurement is automatically superior.

If the question is how likely is one recipient to complain?, the rate is useful.

If the question is how much total complaint handling did this campaign generate?, the count matters.

Thresholds are not proof of favoritism

This becomes important when people compare a giant advertiser with a tiny sender and conclude that one is being protected because it can generate more complaints without disappearing.

That conclusion may be true in a particular case.

But the raw numbers cannot prove it.

A fair comparison needs the same denominator, similar message types, similar recipient acquisition, similar complaint definitions, similar time periods, and evidence about what enforcement actually followed.

Large senders may also face requirements that small senders do not. Gmail classifies a sender that reaches roughly 5,000 messages per day to personal Gmail accounts as a bulk sender and permanently applies additional requirements such as both SPF and DKIM, DMARC, and one-click unsubscribe for promotional mail.

That is explicitly different treatment based on scale.

It is not evidence that the treatment is more lenient.

Complaint metrics describe behavior, not consent history

Even a low complaint rate does not prove that every recipient wanted the mail.

Many people delete unwanted messages instead of reporting them. Some never see a message because it was filtered. Others tolerate marketing they did not particularly request.

A complaint rate is therefore one signal about recipient reaction.

It is not a census of unwanted mail.

Spam Empires operate at scales where denominators matter.

Without them, a thousand complaints can look enormous and one-tenth of one percent can look tiny.

They can describe the same campaign.