Tag: Mailing Lists

Posted on by

Recycled addresses and unreliable claims of an opted-in audience

An email address can stay the same after its meaning changes.

That is bad news for anyone treating a ten-year-old mailing list as a permanent record of human consent.

Mailboxes disappear. Employees leave companies. Role addresses move to new staff. Old consumer accounts go dormant. Some abandoned addresses are eventually repurposed by anti-spam systems as recycled spam traps.

Mailchimp describes recycled traps as addresses that were once real accounts but became inactive and were later used to identify senders who continue mailing stale contacts. See Mailchimp’s explanation of spam traps.

Spamhaus describes a similar process for what it calls dead-address traps: an address can reject mail for a long period and later be reactivated as a trap. See Spamhaus on spamtraps.

The important lesson is larger than spam traps.

A mailing-list record describes a relationship at a moment in time.

Permission belongs to a person and context, not merely an address

Suppose alex@example.com subscribed to a newsletter in 2017.

The sender may have a perfect record showing that Alex clicked a confirmation link.

Years later, the address has been abandoned, reassigned, converted to a role account, or transformed into a trap. The database still says confirmed subscriber.

The database is historically correct and presently wrong.

That is why list maintenance matters.

A sender needs more than evidence that permission existed once. It also needs evidence that the address remains deliverable and that the relationship has not obviously gone stale.

Mailchimp recommends archiving inactive contacts partly because stale addresses can become traps. Spamhaus likewise recommends re-permissioning old lists in some situations rather than assuming an ancient consent record remains meaningful. See Spamhaus guidance for old mailing lists.

Old data can become false without anyone lying

This is a useful Spam Empires problem because it does not require a villain.

A company can honestly say, “this address opted in.”

The current recipient can honestly say, “I never did.”

Both statements can be true if the mailbox changed.

That is what makes provenance and maintenance different tasks.

Provenance answers: how did this address enter the list?

Maintenance answers: does that old event still describe the person receiving the message today?

Industrial marketing systems are very good at preserving records.

Human relationships are less cooperative.

A database can remember consent long after the consenting human has left the building.

Posted on by

Purchased mailing lists and the trade in uncertain consent

An email address is easy to sell.

The history attached to that address is much harder to package.

A purchased mailing list may arrive as a tidy spreadsheet containing names, companies, job titles, locations, interests, or demographic labels. What it often does not make obvious is the exact chain of events that supposedly authorized the buyer to contact each person.

That distinction matters because possession of an address and permission to use it are different facts.

The Federal Trade Commission makes an important U.S. legal distinction here. Its CAN-SPAM guidance says the federal law generally does not require prior opt-in consent before sending commercial email, provided the sender follows the law’s requirements and honors opt-outs. But the FTC also warns that purchased lists can be risky because addresses may belong to people who already opted out or may have been collected through unlawful harvesting or dictionary attacks. See the FTC’s Candid answers to CAN-SPAM questions.

So legal ability to send one kind of commercial message is not the same thing as evidence that the recipient asked for it.

The list loses its story as it changes hands

Suppose a person enters an email address to download a report from Company A.

Did the form clearly say Company A would email them? Did it say their address would be sold? Did it identify the eventual buyer? Did it authorize unrelated marketing? Was the permission limited to one topic? Was the box pre-checked? When did this happen?

A CSV containing person@example.com answers none of those questions.

That is why large email platforms often impose standards stricter than the minimum federal rule. Mailchimp, for example, prohibits purchased, rented, and scraped third-party lists under its current audience requirements. See Mailchimp’s audience requirements.

The platform is protecting more than etiquette. Recipients who do not recognize a sender are more likely to ignore, unsubscribe from, or report the message, damaging delivery reputation for everybody sharing the infrastructure.

Consent needs provenance

A meaningful consent claim needs evidence.

Useful records might include the original collection page, the wording shown beside the form, the date and time of signup, what categories of communication were described, whether third-party sharing was disclosed, the identity of the entity collecting the address, and any later opt-out.

Without that provenance, “they were on a marketing list” is circular reasoning.

The Spam Empires problem is not merely that lists became large.

It is that addresses became tradable inventory while the expectations of the humans attached to them were often reduced to a column nobody bothered to include.

Posted on by

Yahoo Groups: the dissolution of volunteer-run discussion networks

Yahoo Groups began as an acquisition. Yahoo completed its purchase of eGroups in August 2000 and folded the email-list service into its own community products. The result, for most of the 2000s, was one of the largest collections of discussion communities on the web — a place where an interest group was usually a mailing list and a forum at once, reachable by email or by browser.

The lists ran on volunteers

Yahoo supplied the infrastructure; the communities supplied everything else. Each group had an owner and moderators who decided who could join, approved posts in moderated groups, kept spam out, and looked after the files, photos, polls, calendars, and link lists Yahoo offered. These people were volunteers. The person running a local parenting list, a collectors’ club, or a technical group for a niche automobile was doing it for the group, not for pay. The whole service depended on that arrangement: Yahoo hosted the container, and thousands of unpaid maintainers made it worth being inside.

The scale made the model visible but also fragile. A group’s value lived in its message history and its files — years of accumulated answers — plus the small team that kept order. Anyone who owned the infrastructure could take all of that away without asking anyone.

The purge and the shutdown

That is what happened, in stages. In October 2019, Yahoo said it would stop accepting uploads and remove the web-hosted files, photos, polls, calendars, databases, attachments, and message history while groups continued temporarily as email-only lists. Archive Team’s project record documents the shutdown timeline and the rescue effort: roughly 1.48 million public groups with an estimated 2.1 billion messages had been identified, and about 1.8 billion messages had been archived by that stage.

The second stage came a year later. On October 12, 2020, Yahoo announced the full shutdown, citing a steady decline in usage; Yahoo’s shutdown announcement said the service would close in December 2020. No new groups could be created, and group email ended with the platform.

Where the communities went

Yahoo pointed departing users at Facebook Groups, Nextdoor, Google Groups, and, notably, Groups.io, whose paid tier could import a Yahoo group’s member list. Many groups made the move, and the people often survived the transfer; assuming every Yahoo community died confuses the service with its members. What did not migrate cleanly was the archive. Archive Team warned that Yahoo’s GetMyData export omitted categories of material including attachments, databases, polls, photos, and metadata. A group that had stood for twenty years could arrive at its new home with much of its accumulated context missing.

The outcome separates the community from the record. Groups.io still hosts lists that predate the shutdown, and the volunteer moderators largely kept their jobs. What dissolved was the accumulated knowledge: the databases, the files, the threads a new member once browsed before asking a question. The platform died in a clear announcement, but the quieter loss — the years of community history that never got transferred — is the part nobody planned for.