Email aliases for newsletters

Newsletters are the mail you asked for that behaves like the mail you didn't. You subscribe with genuine intent, read three issues, and then it's a recurring interruption you feel vaguely obligated to. Multiply by every "join 10k readers" box you've ever typed an address into, and the inbox stops being a place where anything urgent can be seen.

Aliases don't make newsletters better. They make subscriptions revocable on your terms, which turns out to be most of the problem.

One alias for all, or one each?

The first decision. Both work; they optimise for different things.

One newsletters@ alias for everything is the low-friction option. Every subscription goes to the same address, and that alias becomes a channel you can treat as a unit: pause it during a busy month and every newsletter goes silent at once; unpause and the flow resumes. You lose per-sender attribution — if spam shows up on newsletters@, any of your subscriptions could be the leaker — but for a category this low-stakes, that may be a fair trade.

One alias per newsletter (moneystuff@, benedictevans@) is the precise option. Each subscription is individually pausable and deletable, and a leak is attributable to the exact publication that sold its list — which newsletters, with their sponsor-hungry economics, are not above doing. The cost is a few more seconds per subscription and a longer alias list.

A defensible hybrid: per-newsletter aliases for anything you'd miss, one shared newsletters@ for the impulse subscriptions you already suspect won't survive the month. Tags keep the two populations sortable.

Unsubscribe hygiene, or: whose button is it?

The classic advice is "just unsubscribe", and for legitimate senders it works. But the unsubscribe link has structural problems: it's the sender's button, it sometimes takes "up to 10 business days" to work, occasionally it's a preference-center maze, and for outright spammers it's a liveness check — clicking confirms a human reads this address.

With aliases you hold a button of your own, so the decision tree gets simple:

• Reputable sender you're done with: use their unsubscribe link. It's the polite path, and it cleans their list too.
• Unsubscribe didn't take, or the sender is sketchy: pause the alias, or add a per-alias rule blocking that sender. Effective immediately, no business days involved.
• The address has clearly been passed around: delete the alias (per-newsletter) or rotate it (shared). The whole downstream ecosystem loses you at once.

If a newsletter keeps sending "we miss you" after you've unsubscribed twice, a subject-regex rule matching their favourite phrases is pettily satisfying and completely effective.

One more habit worth keeping: for anything with a known end date — an event's updates, a job-hunt digest — set an expiry date on the alias at subscription time. It unsubscribes you by ceasing to exist, which no sender can override.

Reading newsletters in Telegram

Here's the part that changed the routine for some of us: an alias can forward to a Telegram chat as well as (or instead of) an inbox — each alias takes up to 6 destinations, mixed however you like.

Why bother? Because newsletters and inboxes want different reading modes. An inbox is a task list; unread newsletters sit in it accusing you. A Telegram chat is a feed; you scroll it when you feel like it, and unread messages there carry no guilt. Routing newsletters@ to a dedicated Telegram chat gives every subscription one ambient channel — skimmable on the phone, ignorable without cost, and entirely outside the inbox where actual obligations live.

Practical notes, honestly: long HTML newsletters arrive as readable text with heavier issues attached rather than pixel-perfect layouts — fine for prose newsletters, less lovely for design-heavy promotional mail. Setup is a few minutes with the Telegram guide: create the alias, add the chat as a destination, confirm the verification, done. Your real address appears nowhere in the chain, and the forwarded copies have tracking pixels and tracker parameters stripped, so the "did they open it" beacon in most newsletters reports nothing.

A starting setup

If you're building this from scratch:

1. Create a newsletters@ alias; point it at a Telegram chat, your inbox, or both.
2. Resubscribe your keepers to it — or give each keeper its own alias if you want per-sender control. Do this lazily, as issues arrive, rather than as a migration project.
3. Tag everything newsletter so the population is sweepable later.
4. Old subscriptions still hitting your real address: unsubscribe as they appear. This takes weeks of one-click moments, not an afternoon.

From then on, every "join our list" box gets an alias, and every subscription is one pause away from silence.

The point

The subscribe button was always easy; it's the exit that senders make hard. Aliases move the exit to your side of the door — pause, rule, expiry, delete — and once leaving is free, subscribing gets enjoyable again. Details on rules and expiry are in the getting started guide.