Like most people, I subscribe to far more newsletters than I can realistically read. If you looked at my inbox, you'd probably conclude that I've simply fallen behind. Hundreds of unread messages have become so common that they're almost a badge of honor among people who enjoy newsletters.

The strange thing is that I don't actually regret subscribing to any of them. I still want every one of those newsletters. In fact, I'd probably subscribe to more if I thought I could keep up. The problem isn't the writing. It's where the writing ends up.

That distinction matters because we tend to blame ourselves. We tell ourselves we're disorganized, easily distracted, or simply don't have enough discipline to keep our inbox under control. But I don't think this is a personal failure. I think it's a design problem.

An inbox is remarkably good at helping us process things that need attention. It's much less effective at helping us enjoy things we deliberately chose to read.

Email has always been transactional. Someone needs an answer. A receipt confirms a purchase. A shipping notification tells you a package is on its way. A password reset asks you to take immediate action. Everything about the design of an inbox reinforces the idea that the newest thing deserves your attention first and that the goal is to work your way back to zero.

Newsletters don't fit that model very well. A thoughtful essay from someone you admire doesn't become less interesting because it arrived three days ago. A long-form piece on technology, politics, design, or photography isn't urgent simply because it happens to be at the top of your inbox. Most newsletters don't expire. They wait.

And yet we judge them by the same rules we use for everything else in email. They become part of an ever-growing unread count, quietly transformed from something we wanted to read into something we failed to keep up with.

I wonder if that's why so many people talk about "newsletter fatigue." We assume we've subscribed to too many newsletters, but maybe we've simply been storing them in the wrong place.

The difference becomes obvious if you compare newsletters to almost any other form of reading. No one feels guilty about the books on their nightstand. They aren't seen as a backlog to be cleared before more books are allowed. In fact, most readers I know take a certain comfort in having a small stack waiting for them. It's a reminder that there will always be something interesting to discover when time allows.

Books have always been allowed to wait. In fact, we almost celebrate it. A shelf full of unread books isn't usually seen as evidence of failure. It's evidence of curiosity. Some of those books were bought because we're planning a trip next summer. Others because we suddenly became fascinated by the Civil War, astronomy, photography, woodworking, baking bread, gardening, or fly fishing. Some were recommendations from a friend we trust. Others simply crossed our path at exactly the right moment. We buy them because something about them speaks to the person we are now, the person we think we'll become, or perhaps the person we've been meaning to make time for.

Nobody stands in front of a bookshelf and feels guilty because there are too many possibilities waiting there. Quite the opposite. The unread books are often the most exciting ones because they represent interests we haven't explored yet, places we haven't visited, skills we haven't learned, ideas we haven't wrestled with, and stories we haven't experienced. They wait patiently, asking nothing more than that someday we'll choose one.

Newsletters, on the other hand, inherit all the emotional baggage of email simply because they arrive through the same door. They aren't judged as reading material. They're judged as messages. The unread count becomes an accusation instead of an invitation, and before long we're apologizing for not keeping up with writers we were genuinely excited to hear from.

A book doesn't ask anything of you. It simply waits until you're ready.

A good newsletter is no different.

An inbox, on the other hand, always feels like it's asking for something.

Email makes the opposite promise. Every unread message suggests something unfinished. Something waiting. Something you've neglected. The interface doesn't distinguish between a password reset that expires in an hour and an essay you'll enjoy just as much next weekend. They're both simply unread.

The more I’ve thought about it, the more I’ve come to believe that very little of this has anything to do with newsletters themselves.

A newsletter doesn’t suddenly become urgent because it arrived by email. An essay doesn’t become less thoughtful because it’s been sitting unread for a week. The writing hasn’t changed. Our relationship with it has.

You can even hear it in the language we use. We talk about clearing an inbox. We get caught up. We apologize for being behind. Nobody says they’re behind on their bookshelf. Nobody talks about clearing a novel or catching up on a biography. Those are things we read when we’re ready. Email quietly encourages a different relationship with everything it contains, and after a while we stop noticing that distinction.

Books exist inside a system that assumes reading is leisurely.

Email exists inside a system that assumes everything deserves immediate attention.

I don't think we talk about that enough. We tend to blame ourselves instead. We convince ourselves that we're behind, that we're bad at managing our inboxes, or that we've subscribed to more than we can handle. But what if none of those things are actually true?

What if we've simply inherited an interface optimized for communication and expected it to double as a place for reading?

Maybe that's why unread newsletters feel strangely heavy in a way unread books never do. The writing itself isn't creating that feeling. The inbox is. It quietly assigns urgency to everything it contains, even when urgency makes no sense.

Maybe newsletter fatigue isn’t really about newsletters.

Maybe it’s what happens when everything we’re asked to read is delivered through software designed to help us respond.

I thought I wanted better email rules.

That is usually where the problem starts. A few newsletters pile up. A few more arrive. Some are worth reading, some are not, and suddenly the inbox starts to feel like it has a second job. So you make a folder. Then maybe another folder. Maybe a label. Maybe a rule that moves newsletters out of the inbox before they can make the unread count feel worse.

That helps for a while.

But it never really solved the part that bothered me.

The issue was not only that newsletters were mixed in with receipts, account notices, work messages, shipping alerts, and everything else. The issue was that the software around them still treated them like email. Even when a newsletter was filed neatly into a folder, it was still sitting inside the same tool, surrounded by the same expectations.

Email wants decisions.

Read, reply, archive, delete, forward, mark unread, search, move on.

Newsletters ask for a different kind of attention.

A good newsletter might need ten quiet minutes. Or a Saturday morning. Or a place to sit until I am ready for it. Sometimes I want to read it once and let it go. Sometimes I want to keep it because one paragraph explains something I know I will want again. Sometimes I want it beside older issues from the same writer because the value is not only in one message, but in the collection that builds over time.

That was the thing I wanted a Mac app to respect.

Not another inbox.

Not a full email client wearing a calmer coat.

Not a web service where my reading life disappears into an account somewhere.

I wanted a Mac app for the newsletters I actually wanted to read.

The Mac part mattered to me.

I like software that feels close at hand. I like windows, sidebars, keyboard shortcuts, local files, backups, preferences, and the sense that the app has a real place on the computer where I do my reading and thinking. A lot of newsletters are intimate in a strange way. They are written by people whose work I follow for years. They become part of the texture of my attention. I did not want that collection to feel temporary.

I wanted it to feel kept.

That meant the app had to start from a different premise than email.

Email is still where newsletters arrive. That is good. It means the original message stays in Gmail, iCloud, Outlook, Apple Mail, or whatever account received it. It means replies, forwarding, account settings, folders, and the ordinary truth of email continue to belong where they already belong.

But the reading copy can have a different life.

That is what Letterboxx is built around.

Connect the account you already use. Choose the folders or labels that contain newsletters. Import local copies into a reading library on your Mac. Leave the originals in email. Then read, organize, highlight, search, and back up the copies that matter inside Letterboxx.

That sounds simple, but it changes the mood of the whole thing.

If I open an email app, I immediately feel the weight of everything else waiting there. Even if I am only going in to read one newsletter, I can see the other messages. I can feel the pull of the unread count. I can get distracted by something urgent, something annoying, something administrative, or something I should have answered yesterday.

The reading gets interrupted before it starts.

In a newsletter app, I wanted the opposite feeling.

I wanted to open the app and see writers, topics, and saved reading. I wanted the library to remind me of what I had chosen to keep, not what I had failed to process. I wanted newsletters to belong to Letterboxxes for investing, technology, local news, Apple, cooking, software, or whatever else had become part of my reading life. I wanted old issues to feel findable without making me dig through a mail archive.

I also wanted reading tools that made sense for newsletters specifically.

Some newsletters arrive beautifully formatted. Some arrive with layouts that are a little too clever for their own good. Some are packed with tracking features, ads, and visual noise. I wanted a reader that could show the original when the original was best, but also offer Clean View when that stuff got in the way. I wanted to highlight a passage because it mattered. I wanted search to bring back a half-remembered idea from months ago. I wanted diagnostics because I'm a freaking nerd and like to look at information and understand more about how things are made and where they come from.

And I wanted backups.

That was not an afterthought.

If the app is going to become a reading library, then the library should not feel fragile. Highlights, Letterboxxes, imported copies, rules, and settings are not disposable bits of app state. They are the structure of the collection. They deserve to be protected.

That is the practical side of wanting a real newsletter app for Mac: the library should feel native, readable, and backed up when the collection starts to matter.

This is also why Letterboxx is not trying to replace your email app.

That would be the wrong promise.

The world does not need another place to manage every message in your life. At least, that is not what I wanted to build. I wanted something narrower and more honest: an email newsletter reader for newsletters after they arrive, when they stop being delivery and start being reading.

That distinction keeps the app grounded.

It means Letterboxx can care deeply about newsletters and let you stop pretending that your email client is a newsletter library. It means selected folders matter. It means your original messages stay where they are. It means your Mac can keep your reading collection without also being the source of truth for your entire mailbox.

The more I worked on the app, the more that boundary felt like the whole point.

Email is for communication.

RSS readers are for blogs.

Letterboxx is for newsletters.

That is the category I kept wishing existed.

A Mac app where newsletters do not feel like inbox chores.

A local library where the good ones can accumulate.

An app that understands the difference between clearing a message and keeping an idea.

A place where the writers in my inbox get their own place to hang out.

That is what I wanted.

So I built it.

That sounds simple, but it has become a little unusual.

So much of modern software has a ghostly quality to it. Your stuff is somewhere. Your settings are somewhere. Your history is somewhere. Your data is syncing, indexing, uploading, processing, reconstructing, and quietly becoming dependent on a system you cannot really see.

Sometimes that is fine.

Sometimes it is even wonderful.

But newsletters never felt to me like something that needed to become mysterious.

The whole appeal of a good newsletter is directness. Someone writes something. It arrives in your email account. You read it, save it, ignore it, delete it, forward it, come back to it, or remember one sentence years later.

There is a plainness to that relationship that I like.

I did not want Letterboxx to break that.

I also did not want Letterboxx to pretend it was your email account.

That distinction matters.

Your email account is still the place where the original messages arrive. Gmail, iCloud, Outlook, Apple Mail, IMAP, and whatever else you use already have a job. They keep the source messages. They handle replies, forwarding, sending, account settings, server folders, labels, and the ordinary truth of email.

Letterboxx is not trying to replace that.

Letterboxx is for the reading copy.

That is the idea I kept coming back to while building it. A newsletter can arrive in email and still deserve a different life after delivery. It can have an original that stays in your account and a local copy that becomes part of a reading library on your Mac.

The original remains where it belongs.

The reading copy gets a room of its own.

Local-first is partly a technical choice, but for Letterboxx it is also a feeling.

It means the library you build should feel close at hand. It should not feel like a remote service you are borrowing access to. It should feel like a collection on your Mac: newsletters you chose, topics you organized, highlights you saved, settings you shaped, and backups you control.

That does not mean everything is isolated from email. Letterboxx still connects to the accounts you choose. It still imports from folders or labels that already mean something in your mail setup. If you use Gmail or IMAP, Letterboxx can look at selected sources and bring newsletter copies into the app.

But the goal is not to mirror every corner of the account.

The goal is to build a reading library.

That is a quieter promise.

It is also a safer one.

If software says it is going to mirror your email, you naturally start asking email-client questions. Does it know every folder? Does it track every change? Does it behave exactly like Mail? Does it become another place where account truth can drift?

Letterboxx should not ask you to think that way.

Your mail account keeps being your mail account.

Letterboxx keeps the newsletters you decided were worth reading there.

This is why selected folders matter. Some people already have a Newsletter label in Gmail. Some have an iCloud folder. Some have years of topic folders they built without realizing they were quietly making an archive. Some people want a fresh account just for subscriptions. Some want to bring history forward from old folders.

All of those are valid.

The point is intention.

If you want the practical version of that boundary, the how Letterboxx works guide explains how selected folders become local reading copies without asking Letterboxx to become your email account.

You choose the sources. Letterboxx imports copies. Then those copies can become something email folders never quite became for me: a library with its own shape.

In a local-first reading library, a newsletter is not only a message. It can sit beside related issues. It can belong to a Letterboxx for investing, technology, local news, Apple, design, cooking, or whatever your reading life has collected. It can be opened in a reader instead of an inbox. Clean View can remove any obtrusive ads. A highlight can preserve the paragraph that made the whole issue worth saving.

Over time, that local library starts to feel different from an inbox.

It is not asking to be emptied.

It is asking to be returned to.

That is the part I care about most.

Newsletters are easy to lose because they are delivered through a system designed for throughput. Email wants to move. It wants to be scanned, processed, replied to, archived, searched for, or deleted That is useful, but it is not always how reading works.

Reading accumulates.

It gathers writers, questions, fragments, half-remembered ideas, and the strange little trails of attention that make a person feel like themselves.

If I am going to build a library out of that, I want it to feel durable.

I want backups.

I want the originals to remain in email.

I want the reading copies to be close enough that I understand what the app is doing with them.

I want to know that my highlights, Letterboxxes, rules, newsletters, and settings are part of something I can protect.

That is also why newsletter backup and restore matters: once a local library starts carrying history, it deserves a recovery plan.

That is what local-first means here.

Not a slogan.

Not a rejection of the internet.

Not pretending email accounts do not exist.

Just a preference for keeping the reading library understandable, recoverable, and grounded on the Mac where I actually read.

There is something calming about that.

Maybe it is because newsletters themselves are so personal. They are not just content units. They are recurring relationships with writers and topics. They are the things you keep because they keep making you think. They are the old issue you find again and realize it marked the start of some interest you still have.

That kind of collection deserves software that does not make it feel disposable.

Letterboxx is local-first because the newsletters you keep should feel kept.

Your email account can keep the originals.

Your Mac can keep the reading library.

And you can decide which newsletters are worth bringing into that room.

That is where I started, anyway.

Make a folder for newsletters. Maybe make one for investing. Maybe make one for Apple. Maybe make one for local news. If a newsletter arrives and it belongs somewhere, file it there. If you are feeling fancy, set up a rule so it happens automatically.

For a while, that feels like progress.

And to be fair, it is progress. A folder is better than letting everything pile up in the inbox. A rule is better than manually dragging messages around forever. A label is better than trying to remember which sender wrote the thing about the thing you meant to read three weeks ago.

But at some point, the folder stops feeling like organization and starts feeling like storage.

That distinction matters.

Storage means the newsletters are somewhere. Organization means they are arranged in a way that matches how you actually think about them.

For me, the big categories have always been pretty obvious: technology, investing, Apple, software, business, and local news. Those are the subjects that keep pulling me back. They are also the subjects where old newsletters become useful in different ways.

A technology newsletter is often about motion.

Something launched. Something changed. Something broke. Someone is trying a new model. A company made a bet. A developer found a clever approach. Half the value is in the freshness, but the other half is in the pattern you start to see after reading enough of them. One issue might be a news item. A year of issues becomes a map of where the industry thought it was going.

An investing newsletter works differently.

Investing writing ages in strange ways. Some of it expires immediately. Some of it becomes more interesting later because you can compare the argument to what actually happened. A market note from three years ago might not tell you what to buy today, but it can remind you how people felt at the time. It can show the assumptions that were obvious then and questionable now. It can make you more honest about your own memory.

Local newsletters are different again.

They are often small, practical, and specific. A city council note. A new restaurant. A school board issue. A road project. A local business opening or closing. A community event that only matters because it happened near you. Some of it is temporary. Some of it becomes part of the record of a place.

Those categories do not want the same treatment.

That is where plain email folders started to feel too blunt for me.

In Mail, everything is still shaped like mail. The folder can say "Investing" or "Technology" or "Local", but the surrounding software still asks the same questions. Is this read? Should it be archived? Should it be replied to? Is it part of the inbox? Is it clutter? Should I clear it?

Those are mail questions.

They are not always reading questions.

When I organize newsletters in Letterboxx, I try to organize around the way I expect to return to them.

That usually means making Letterboxxes for durable interests instead of tiny perfect categories. I do not need a separate place for every sender. I do not need twenty categories just because twenty newsletters exist. I need a few shelves that make sense when I open the app with ten minutes to read.

Technology.

Investing.

Apple.

Local.

Software.

Maybe one or two project-specific Letterboxxes when something in my life has its own gravity.

The goal is not taxonomy for its own sake. The goal is to make the next reading decision easier.

If I am in an investing mood, I want to see the investing pile. If I am catching up on what is happening around town, I want local newsletters together. If I am thinking about product design or Mac software, I want the technology and software writing close enough that the connections can show up.

That is one of the reasons I like the word Letterboxx.

It is not only a folder. It is a place for a kind of recurring attention.

The practical setup is simple.

Email still receives the newsletters. Gmail, iCloud, Outlook, a custom IMAP account, whatever you already use. I keep or create folders and labels there when they are useful, because the original messages still belong to the mail account. Then Letterboxx imports copies from the folders I choose and lets those copies live in a reading library on my Mac.

For the step-by-step version, the guide to organizing newsletters with Letterboxxes turns this habit into a concrete setup flow, and the broader product page explains how to organize email newsletters without making inbox folders do all the work.

The difference is what happens after import.

In email, a newsletter folder is still surrounded by everything else email wants from me. In Letterboxx, the same newsletter can become part of a collection. It can sit beside other issues in the same topic. It can be opened in a dedicated reader. It can be cleaned up when the HTML gets noisy. It can be highlighted when one paragraph is worth keeping. It can be searched later when I remember the idea but not the sender.

That last part matters more than I expected.

Search is not only about finding a message. It is about recovering a thread of attention.

Sometimes I remember a phrase from a technology newsletter but not who wrote it. Sometimes I remember an investing idea but not the date. Sometimes I remember that a local issue came up months ago, but I need to find the original note before I can understand the new one.

When newsletters are scattered across folders, accounts, and years of ordinary email, that kind of search feels like digging through a garage.

When they are gathered into a reading library, it feels more like looking across a shelf.

Not perfectly. I still make messes. I still over-save things. I still create categories that later feel too clever and have to be renamed. But the mess is at least the right kind of mess.

It is a reading mess.

That has become my rule of thumb.

If the newsletter belongs to a conversation I might want to continue later, it deserves a Letterboxx.

If it is mostly a notification, a sale, a one-time update, or something I only need to glance at once, it can stay in email or disappear.

That line is personal. Somebody else's local-news pile might be my disposable update. My investing archive might look excessive to someone who reads differently. That is fine. The point is not to organize newsletters according to some universal system. The point is to let the library reflect what you keep coming back to.

The best categories are the ones that still make sense after the novelty wears off.

Technology is still technology after a month.

Investing is still investing after a year.

Local is still local after the event has passed, because places have memory too.

Those are the categories I want close at hand.

Not because every issue is important.

Because enough of them are.

And because when newsletters are organized around the subjects I actually care about, they stop feeling like inbox leftovers.

They feel like a library I am building on purpose.

That sounds obvious, but it is easy to forget when newsletters are involved.

An email app has a job. It receives things. It lets you reply, forward, archive, delete, flag, search, and move on. It handles conversations, receipts, account notices, calendar invitations, password resets, shipping alerts, support threads, work updates, and the thousand other little pieces of digital life that arrive because someone or something needed to reach you.

For that kind of work, Mail makes sense.

The problem is that newsletters arrive through the same door.

They show up in the same list as everything else. A long essay from a writer you love sits next to a two-factor code. A market analysis you want to think about later sits next to a shipping notice. A thoughtful weekly dispatch sits under a receipt, above a login alert, and beside the message you actually need to answer before lunch.

The inbox does not know the difference.

It sees messages.

You see reading.

That mismatch is the whole problem.

I have tried the usual answers. I have made folders. I have made rules. I have made special newsletter labels. I have flagged messages, archived messages, searched for old messages, and told myself that the system was working because the messages were technically still there.

And technically, they were.

But reading is not only a storage problem.

If all you need is a place where newsletters can exist, Mail can do that. It can store years of them. It can search them. It can file them into folders. It can keep the originals safe in the account where they arrived.

What Mail cannot easily do is change the feeling around them.

Inside Mail, every newsletter inherits the emotional weather of the inbox. Even a newsletter you genuinely want to read can feel like one more unread thing. It becomes part of the queue. Part of the count. Part of the background pressure to clear, process, archive, and be done.

That is fine for a lot of email.

It is a strange way to treat writing.

The best newsletters are not tasks. They are small publications. They are recurring letters from people whose thinking you want in your life. They are essays, briefings, commentary, analysis, recommendations, and conversations that build up over time.

When those newsletters stay in Mail, they are surrounded by messages that want a completely different kind of attention.

A receipt wants to be found when needed.

A work message wants a response.

A password reset wants to expire.

A newsletter wants time.

That is why folders never quite solved it for me. A folder can separate newsletters from the inbox, but it still lives inside the same tool, with the same mental model. I am still in email. I am still one click away from the rest of the pile. I am still surrounded by the machinery of communication.

Sometimes that is exactly what I want.

But when I sit down to read, I want a different room.

I want to see the newsletters as a collection, not as a mail-management workaround. I want writers and topics to have shape. I want old issues to feel findable without feeling buried. I want to save a passage because it mattered, not because I am trying to keep track of another message.

I want the original email account to remain trustworthy and familiar, but I do not want the inbox to decide what reading should feel like.

That is the split Letterboxx is built around.

Mail keeps the originals. Letterboxx keeps the reading copies.

For a feature-by-feature view of that split, compare an email client with a newsletter reader, or start with the shorter email newsletter app overview.

The distinction is small, but it changes the whole room.

In Letterboxx, a newsletter can stop acting like an email task. It can live in a Letterboxx for a topic, writer, project, or interest. It can open in a reader instead of an inbox. It can use Clean View when the HTML gets noisy. It can be highlighted when a paragraph is worth keeping. It can be searched later as part of a reading library instead of recovered from a pile.

None of that means Mail was wrong.

It means newsletters have a second life after delivery.

The email account is still useful because it receives the message and keeps the original. Mail is still useful because communication belongs there. If a newsletter needs a reply, a forward, an unsubscribe, or account-level handling, the email app is still the right place to go.

But if a newsletter is something you want to read, remember, organize, and return to, it deserves more than being treated like another inbox item.

That is the problem with reading newsletters in Mail.

Not that Mail is bad.

Not that folders are useless.

Not that search does not work.

The problem is that newsletters are reading material wearing an email costume.

Once you notice that, it is hard to unsee.

You start to realize that the issue was never just where the newsletters were stored. It was what the software around them was asking you to do.

The inbox asks you to get through things.

Reading asks you to stay with them.

Those are different instincts, and they deserve different spaces.

That is the strange thing.

They use the same pipes. They land in the same inbox. They have senders, subjects, timestamps, unread states, and all the other little signals that make an email client understand what it is looking at.

But the experience is different.

A normal email usually wants something from me.

Reply to this. Confirm that. Notice this update. Save this receipt. Click this link. Reschedule this meeting. Check this account. Deal with this before it becomes a problem.

Even when the message is small, there is often a tiny bit of obligation attached to it.

Newsletters can have obligation too, especially when I have let them pile up for too long. But the good ones do not begin there. They begin with a different promise.

Here is something worth reading.

That is a different relationship.

When a writer sends a newsletter, they are not usually asking me to answer. They are not trying to close a loop in the same way a work message or support thread might. They are bringing me a piece of thinking. A story. A set of links. A market note. A product idea. A personal dispatch. A weekly rhythm.

The inbox sees a message.

I see a small publication.

That difference changes everything.

Email is usually about exchange. Someone sends, someone responds, a task moves forward, a question gets answered, a transaction gets recorded.

A newsletter is usually about attention. Someone has spent time noticing, thinking, collecting, writing, editing, and arranging something so it can be received later by people who care about that subject.

It may be delivered by email, but it is shaped more like reading than correspondence.

That is why the best newsletters start to feel familiar over time. You learn the writer's cadence. You notice the recurring sections. You know who likes a sharp intro, who buries the best line near the end, who always has one link you would have missed, who is generous with context, who writes like a friend leaning across a table.

Ordinary email rarely builds that kind of relationship.

Newsletters can.

This is also why they are so easy to underestimate. Because they arrive in the inbox, they inherit all the assumptions of the inbox. They look like another thing to clear. Another unread number. Another item in the stack.

But if you zoom out, newsletters are one of the odd little miracles of the modern internet.

Independent writers can build direct relationships with readers. Analysts can publish without waiting for a magazine slot. Local journalists can reach people who care about a city or county. Experts can explain a field from the inside. Curious people can share what they are learning as they learn it.

And all of it arrives in the most ordinary place possible.

Your email.

That ordinariness is part of the charm, but it is also part of the problem.

Email clients are not wrong to treat newsletters as messages. Technically, that is what they are. The original belongs in the email account. The sender, timestamp, headers, and account history all matter. I do not want those things hidden or broken.

But the reading experience asks for something else.

It asks for a quieter surface.

It asks for a sense of collection.

It asks for a place where a recurring writer can be more than a sender in a crowded list.

It asks for the ability to keep a passage because it changed the way you thought about something, not because you are managing an inbox.

That is where newsletters start to feel different from email.

They are delivered through a communication system, but many of them belong to a reading life.

I notice this most clearly when I search old newsletters. If I search for a receipt, I usually want proof of something. If I search for a support email, I want a detail. If I search for an account notice, I want the date, the link, the number, the exact thing that lets me move on.

When I search newsletters, I am often looking for a thought.

I remember someone explained this well.

I remember there was a paragraph about that.

I remember a writer connected two ideas I had not connected before.

I remember reading something that changed my mind, but I do not remember the subject line.

That kind of search does not feel like retrieving email. It feels like walking back through notes in the margins of a reading life.

The same thing happens with folders.

A mail folder can hold newsletters, but over time a good newsletter folder starts to feel less like a folder and more like a shelf. Investing. Apple. Local news. Design. Software. Cooking. Whatever the topic is, the folder stops being a mail-management trick and starts becoming evidence of what has held your attention.

That is the part I care about.

Not just the messages.

The attention.

The writers you kept listening to.

The topics that kept pulling you back.

The ideas that survived past the day they arrived.

A newsletter may begin as an email, but if it matters, it does not stay only that. It becomes part of a collection. Sometimes a private one. Sometimes a messy one. Sometimes one you do not even realize you have been building until you look back and see years of curiosity sitting in a folder.

Letterboxx exists because that difference felt worth respecting.

I did not want to pretend newsletters were not email. They are. The originals stay in the account where they arrived. Your email app still handles communication, account truth, replies, forwarding, sending, and the rest of the normal mail job.

But I also did not want newsletters trapped forever inside the mood of email.

So Letterboxx gives the reading copy a different room.

One where newsletters can be organized by topic, opened in a reader, cleaned up when the HTML gets noisy, highlighted when a passage is worth keeping, searched when an idea comes back, and backed up as part of the local library you have built.

That is the product version of the feeling: an email newsletter reader for writing that arrives through email but deserves a calmer place to live.

That is not because newsletters are less than email.

It is because, often, they are more specific than email.

They are letters and essays and briefings and little magazines and private archives and recurring conversations with people whose thinking you want nearby.

They feel different because they ask for a different kind of attention.

And when something asks for a different kind of attention, sometimes it deserves a different place.

I understand the appeal. Of course I do. There is a real satisfaction in clearing a pile, answering what needs an answer, deleting what can be deleted, archiving what is done, and watching the unread number disappear. Email can become a pressure system if you let it. Emptying the inbox can feel like opening a window.

But newsletters never fit that ritual for me.

A receipt can be processed. A shipping notice can be checked and forgotten. A meeting update can be read, acted on, and moved along. Those messages have a job, and once the job is done, they mostly stop asking for anything.

A good newsletter is different.

It arrives by email, but it is not really email in the same way. It might be an essay. It might be a weekly briefing. It might be a long analysis, a collection of links, a personal dispatch, a piece of reporting, a note from someone whose work I have followed for years.

The inbox sees all of that as another message.

I do not.

That is the tension. Email clients are good at helping me decide what needs attention now. Newsletters are often valuable because they deserve attention later.

Those are very different promises.

The inbox asks, "Are you done with this?"

Reading asks, "Do you want to keep this close?"

For a long time, I treated those questions as if they were the same. I would open Mail, skim a newsletter, maybe star it, maybe file it into a folder, maybe tell myself I would come back to it. Sometimes I did. More often I simply carried the vague sense that something worth reading was buried somewhere under everything else.

That is not a failure of email. It is just the wrong room.

Mail is a workshop. It is where things come in, get handled, get answered, get sorted, and get sent back out. It is active and transactional because that is what most email needs.

But my newsletters did not feel transactional. The best ones felt more like books, magazines, letters, clippings, and notes saved for a quieter hour.

They needed a shelf.

Not a perfect shelf. Not a productivity system with a halo over it. Just a place where newsletters could stop competing with receipts and password resets and shipping alerts. A place where I could see the writers and topics I cared about without first walking through the whole machinery of email.

That is the feeling I kept chasing while building Letterboxx.

I did not want another inbox with a different coat of paint. I wanted a reading shelf for things that happened to arrive through email.

That distinction matters more than it may sound.

If a newsletter is only inbox material, then the best outcome is to clear it. Read it fast, archive it, delete it, move on. Anything left behind becomes clutter. The unanswered question is always whether it has been processed.

But if a newsletter is reading material, the best outcome is different. It can be saved without guilt. It can be organized by topic. It can be highlighted. It can be searched when a half-remembered idea comes back weeks later. It can sit with other issues from the same writer and slowly become part of a collection.

That is not clutter to me.

That is a library taking shape.

This is why "Inbox Zero" never felt like the right goal for my newsletters. I do not want my reading life to disappear just because I was efficient. I do not want every issue flattened into the same yes-or-no question as an account notice. I want some things to remain available because they are still alive in my head.

A reading shelf is allowed to have unfinished things on it.

That is kind of the point.

There are newsletters I want to read tonight, newsletters I want to save for Saturday morning, newsletters I want to skim and come back to, newsletters I want to keep because one paragraph changed the way I understood something. There are writers whose work I follow not because each issue demands action, but because over time their thinking becomes part of my thinking.

An inbox is not built to honor that relationship. It can store the messages, sure. It can search them. It can file them. But the emotional gravity is wrong. Everything in an inbox eventually feels like a task.

Letterboxx tries to change that gravity.

It imports local copies from the folders you choose. The original messages stay in your email account. That part matters. I do not want software to make my mail account feel less familiar or less trustworthy. Gmail, iCloud, Outlook, Apple Mail, and IMAP can keep doing the email job.

If that distinction is the part you want to understand first, start with how Letterboxx works, then look at the broader email newsletter reader workflow.

Letterboxx takes the reading copy and gives it a different job.

Now a newsletter can live in a Letterboxx for investing, technology, local news, cooking, design, Apple, or whatever else your reading life has quietly collected. It can open in a reader instead of an inbox. Clean View can make messy newsletter HTML feel calmer. Highlights can mark the passages worth keeping. Search can bring old ideas back without asking you to remember exactly which folder they were buried in.

None of that is about getting to zero.

It is about making room.

I still understand the relief of an empty inbox. Some days I want that too. But I do not want to confuse relief with reading. Clearing email is not the same as keeping ideas. A calm inbox is useful. A shelf full of writing that mattered to you is useful in a different way.

I think that is why newsletters are so easy to underestimate.

They arrive in the same place as disposable messages, so we start treating them as disposable too. But the best newsletters are not disposable. They are recurring conversations with people who are paying attention to something. They are small publications. They are personal archives. They are little packets of someone else's curiosity arriving on a schedule.

When enough of them matter, they stop being a pile.

They become a reading life.

That is what I want Letterboxx to respect.

Not an empty inbox.

A shelf worth coming back to.

Actually, let’s be honest. “Pack rat” is probably the charitable version. Depending on who you ask, there’s a reasonable argument to be made that I’m a digital hoarder.

If future archaeologists ever gain access to my email archive, they’re going to learn an alarming amount about my life. They’ll know what I bought, when I bought it, where I bought it from, and probably what I paid for it. They’ll find receipts, invoices, warranty information, utility bills, account notices, support tickets, and all the other digital breadcrumbs that quietly accumulate over a lifetime.

The funny thing is that I know exactly why I keep most of it.

Every so often I’ll find myself trying to remember something. When did I buy that? What was the model number? Which account did I use for that service? A quick search later and there it is. Past Chris helping Present Chris — and probably even Future Chris — solve a problem. Those emails are records. They’re useful because they document something that happened.

For years, I assumed newsletters belonged in that same category.

They arrived in my inbox alongside work messages, bills, receipts, account notices, and all the other things competing for my attention. Sometimes I read them right away. Sometimes I saved them for later. Sometimes “later” turned into weeks, months, or even years.

But unlike most email, I almost never deleted them. At the time, I assumed they were just another type of email. At least, that’s what I thought. The reality was different, but I didn’t realize it until much later.

Over the years, I’ve subscribed to newsletters about investing, technology, Apple, software, business, and whatever else happened to capture my attention. Some were written by journalists. Some by analysts. Some by independent writers building an audience one issue at a time. Some had been showing up in my inbox for so long that seeing their name felt as familiar as hearing from an old friend.

One day it hit me that I wasn’t saving those newsletters for the same reason I saved receipts. I wasn’t saving them because they documented a transaction. I wasn’t saving them because they proved something happened. I was saving them because I cared about the people writing them.

That sounds obvious now, but it wasn’t obvious to me at the time.

Many of the newsletters I follow are written by people who spend hours every week thinking, researching, writing, editing, and refining something they hope will be worth a few minutes of my attention. They pour their expertise into it, sure, but also their humor, curiosity, frustrations, experiences, and personality. Over time, you get to know their voice. You learn who makes you think, who makes you laugh, who has great taste for product recommendations, and who consistently points you toward ideas you would have missed on your own.

Some of those writers have been showing up in my inbox for years — longer than many software applications I’ve used, and hell, even longer than some jobs I’ve had, come to think about it. Long enough that opening one of their newsletters doesn’t really feel like checking email anymore. It feels like hearing from someone.

The longer I thought about it, the more newsletters reminded me of something much older: letters.

Actual letters. Not business correspondence, bills, or account notices, but the kind people used to write because they had something to say and someone they wanted to say it to.

The medium changed. Ink and paper became pixels, ones, and zeros. But the relationship didn’t.

A good newsletter still feels like hearing from someone.

That’s why I saved them.

Or at least, that’s why I save the good ones.

Not every newsletter survives. Plenty get deleted. Plenty get unsubscribed from. Plenty turn out to be less interesting than I hoped they would be.

But the ones that stay? The ones that teach me something, make me laugh, challenge my assumptions, or arrive at exactly the right moment? Those are the ones that stick around.

And once I saw that, I couldn’t unsee it.

In reality, I had spent years building a library.

One folder in particular finally made me realize this. It was called Berkshire Hathaway.

At some point over the years I had started filing investing newsletters into that folder. By the time I really stopped and looked at it, it contained years of commentary, annual meeting notes, investing ideas, market observations, and writing from people I respected. Some of those messages had survived multiple computers, multiple Apple Mail client versions, and multiple chapters of my life.

The strange thing was that I wasn’t treating any of it like email.

I wasn’t replying to it. I wasn’t forwarding it. I wasn’t trying to get to Inbox Zero.

I was treating it like a bookshelf.

That’s where this story eventually intersects with Letterboxx.

When I started building the app, one of the first things I did was create a brand-new email address dedicated entirely to newsletters. Then I spent weeks updating subscriptions I’d accumulated over more than twenty years. New newsletters began flowing into that new address through Letterboxx. Everything felt clean, organized, and intentional.

For the first time in years, when I wanted to read my new newsletters, I didn’t open Mail.app on my Mac. Instead, I fired up my still-work-in-progress instance of Letterboxx in Xcode and, to be honest, it felt fucking AMAZING. Finally! Now I finally had a way to separate the things I needed to read from the things I wanted to read. I loved it.

No work email.

No bills.

No spam.

No receipts.

No account notices.

Just newsletters.

For the first time, it felt like that part of my digital life had its own home.

Except it didn’t.

Because all of the newsletters that mattered most to me were still somewhere else.

The investing newsletters in my Berkshire Hathaway folder were still sitting in my old account in Mail.app. The technology newsletters I’d been following for years were still there too. So were countless others I’d collected over the years. Apple. Design. Software. Technology. Investing.

Looking back, those folders weren’t really collections of newsletters. They were collections of interests. Collections of curiosities. Collections of ideas that had seemed important enough at one point in my life that I wasn’t willing to throw them away.

If someone spent an afternoon browsing through those folders, they’d probably learn more about what fascinated me over the last twenty years than they would from my resume.

And the more I used Letterboxx, the stranger that felt.

My current newsletters were in one place. My history was in another.

Nothing was technically wrong. Everything still worked. I could still access those email folders in Mail whenever I wanted. But it felt strange and wrong to have my newsletters scrambled across apps and accounts.

The collection wasn’t together.

Looking back, I think that’s what bothered me so much.

Those folders weren’t just storage. They were a map of the things I’d cared about over the years. Investing. Apple. Software. Design. Technology. They represented countless hours spent reading, learning, wondering, and occasionally changing my mind.

Having them split apart felt less like an organizational problem and more like finding chapters of the same book shelved in different rooms.

The thing that surprised me most was that I wasn’t frustrated because the software wasn’t working. I was frustrated because the story wasn’t complete. The newsletters arriving today were separated from the newsletters that had shaped how I thought years earlier. My current interests were in one place. My history was in another.

I wanted them together. Not because they were email. Because they were part of the same collection. And maybe because the "pack" portion of being a digital pack rat really needed things to stay together.

That’s ultimately what led me to add support for connecting specific folders and multiple accounts. So I updated Letterboxx to look beyond a single inbox. I connected my personal email account, pointed Letterboxx at my Berkshire Hathaway folder, and watched years of newsletters appear alongside the new ones arriving every day.

The practical side of that story now lives in how Letterboxx works: choose the folders that matter, import local copies, and let the original messages stay in email.

Nothing was moved. Nothing was taken away from my mail account. For the first time, everything simply lived together.

And for reasons that are probably difficult to explain to anyone who isn’t also a digital pack rat, that felt like fucking magic to me.

That experience changed the way I think about newsletters and Letterboxx. It went from being a place to start over with newsletters to a place where you could also bring your history with you.

I still save newsletters. Probably more than I should. And I still have email folders that future archaeologists would find fascinating.

But I’ve stopped thinking of newsletters as electronic mail.

They’re the thing you didn’t know you needed to read that day.

The writer who makes you laugh after a difficult day.

The person who explains something you’ve been struggling to understand.

The idea that sends you down a rabbit hole for the next three hours.

The perspective that changes your mind.

The encouragement you needed to hear from someone you’ve never actually met.

Over the years, some of those writers become familiar companions. Their newsletters mark different chapters of your life. You remember where you were when you first subscribed. You remember the ideas they introduced you to. You remember the moments when something they wrote arrived at exactly the right time.

That’s why I save them.

Not because they’re email.

Because they’re people.

And because some of the most meaningful things we carry with us arrive one message at a time.