Youvecottmail

In September 1915, the House of Commons took up a resolution to raise the price of a telegram. The proposed rate: ninepence for twelve words, and a halfpenny for each additional word. The resolution was reported, read a second time, and then adjourned for further consideration in October. It was not a final tariff. It was a proposal, debated in public, with the cost of every word on the table.

That is the artifact I want to start with, because it makes visible something that most writing advice treats as a matter of taste. When a message is priced by the word, brevity stops being a virtue and becomes a budget line. The sentence is no longer a free-form utterance. It is a quantity of billable units, and the writer knows it before the first word is set down.

This is not a story about how email descends from the telegram. It is a story about what happens to prose when the container’s cost structure is visible to the person writing inside it. The telegram is the clearest historical case we have. The newsletter is the case most of us are living in now.

A tariff is an editorial instrument

The 1915 resolution is specific enough to be useful. It proposed that written telegrams throughout the United Kingdom be charged at a rate not exceeding ninepence for each telegram of twelve words, or for each telegram of fewer than twelve words, and a halfpenny for each additional word. Press telegrams were priced separately, by the hundred or seventy-five words depending on the hour, with an additional charge for each additional address.

Read that as a writer rather than a historian. The first twelve words are a flat fee. The thirteenth word costs a halfpenny. The fourteenth costs another. Every word after the twelfth has a marginal price, and the writer can calculate it. The container is not neutral. It has an opinion about how long your message should be, and it expresses that opinion in coin.

But the 1915 resolution was not the only arrangement, and it was not settled. Thirty-two years earlier, in July 1883, the Postmaster General, Fawcett, answered a question about two competing schemes for reducing the minimum charge for Post Office telegrams to sixpence. Scheme 1 would have abolished free addresses and charged a halfpenny for each word, including the address, with a sixpence minimum. Scheme 2 would have kept the receiver’s address free but charged for the sender’s, with sixpence for the first five words and twopence for each additional five words.

Fawcett conceded that under either scheme, the charge for messages containing twenty words in the body of the telegram might be greater than it then was. He also noted that no decision would be made until the next session, and that if addresses were charged or twenty-word messages cost more, a Bill would be required because the present tariff was fixed by Act of Parliament.

This is the part that matters for anyone who writes inside a platform. Per-word pricing was not a natural property of the telegraph. It was a policy choice, contested, revised, and sometimes abandoned. The brevity it produced was a response to a specific institutional arrangement. It was not a universal editorial virtue that the medium somehow discovered.

Telegraphese as a named register

The style that grew up around these tariffs has a name. Telegram style, telegraph style, telegraphic style, or telegraphese is a clipped way of writing that abbreviates words and packs information into the smallest possible number of words or characters. It originated in the telegraph age, when telecommunication consisted only of short messages transmitted by hand over the telegraph wire.

The mechanism was straightforward. Telegraph companies charged by the number of words in a message, with a maximum of fifteen characters per word for a plain-language telegram and ten per word for one written in code. The style developed to minimize costs while still conveying the message clearly and unambiguously.

Notice the constraint on both ends. You are charged per word, but a word is not unlimited in length. Fifteen characters for plain language, ten for code. So you cannot simply concatenate everything into one enormous billable unit. You have to choose words that fit the character limit and still carry meaning. The tariff disciplines the sentence; the character limit disciplines the word.

This is a more interesting constraint than “be concise.” It is a constraint with two dimensions, and it forces the writer to think about the unit of billing rather than the unit of meaning. A word is not a thought. A word is a package with a size limit and a price.

The code-word economy and its warning

The extreme case of per-word compression is the commercial code. Through the history of telegraphy, many dictionaries of telegraphese, codes, and ciphers were developed, each serving to minimize the number of characters or words needed to transmit a message. The drivers were different for different parties: for telegraph operators, the resource cost and limited bandwidth of the system; for consumers, the cost of sending messages.

The Adams Cable Codex, published in 1894, assigned full phrases to single code-words. “Emolument” meant “Think you had better not wait.” “Emotion” meant “Think you had better wait until…” “Emotional” meant “Think you had better wait and sail…” “Empaled” meant “Think well of party mentioned.” “Empanel” meant “This is a matter of great importance.”

The ABC Universal Commercial Electric Telegraphic Code, published in 1901, went further and used invented, English-like words. “Nalezing” meant “Do only what is absolutely necessary.” “Nalime” meant “Will only do what is absolutely necessary.” “Nallary” meant “It is not absolutely necessary, but it would be an advantage.” “Naloopen” meant “It is not absolutely necessary, but well worth the outlay.”

Here is the warning. When a single billable unit can carry a whole phrase, the writer is no longer choosing words. The writer is choosing which pre-fabricated units to spend. The vocabulary has been compressed into a menu, and the menu was built by someone else, for the convenience of the billing system. The code-word economy is the limiting case of per-unit pricing: maximum compression, minimum authorial discretion.

This is not a model to copy. It is a boundary marker. It shows where the logic of per-word pricing leads if you follow it without resistance. The writer becomes a selector of codes, not a maker of sentences.

What the average telegram tells us about the discipline

The average length of a telegram in the 1900s in the United States has been reported as 11.93 words, with more than half of messages at ten words or fewer. That figure comes from a Wikipedia article on telegram style, which cites David Hochfelder’s The Telegraph in America, 1832–1920. I have not independently verified the underlying study, so treat the number as a reported finding rather than a settled fact.

But the shape of it is plausible and useful. If the first twelve words are a flat fee and the thirteenth costs extra, you would expect a clustering at or just below the threshold. The average of 11.93 words is consistent with a population of senders who understood the tariff and wrote to it. The container did not just permit brevity. It produced a specific distribution of message lengths.

That is the practical lesson for anyone writing inside a platform today. The default length of a newsletter, the character limit of a subject line, the preview text that gets truncated at a certain pixel width — these are tariffs, even when no money changes hands. They are pricing mechanisms denominated in attention, deliverability, or interface real estate. The writer who does not see the price is still paying it.

The newsletter as a priced container

Here is where I want to be careful, because the analogy is easy to overdraw. Email did not inherit telegraphic style. The Wikipedia article on telegram style notes a comparison to modern text messaging, but that passage is flagged as unsourced and weasel-worded, and I am not going to lean on it. The lineage claim is not supported by the evidence I have.

What is supported is a structural observation. The telegram sender wrote inside a container with a visible per-unit cost. The newsletter writer writes inside a container with costs that are usually invisible but no less real. The subject line has a character limit before it truncates in the inbox. The preview text has a pixel limit before it cuts off. The send itself has a deliverability cost that varies with list hygiene and engagement. The body has a scroll depth beyond which most readers do not go.

None of these are priced in pence per word. But they are priced. And the writer who treats them as neutral — who writes the same way regardless of the container — is making a choice without knowing it.

The telegram’s contribution to this conversation is not a style to imitate. It is a demonstration that when the price is visible, the prose changes. The 1883 and 1915 debates show that the price was a contested policy, not a fact of nature. Which means the brevity it produced was a response to a specific arrangement, not a universal good.

A hypothetical, clearly labeled

Suppose you ran a newsletter where each additional section beyond the first cost you something — a deliverability penalty, a reader-attention tax, a per-segment fee from your sending platform. I am inventing this scenario as an illustration, not reporting a real pricing structure. But suppose it were true.

How would you draft differently? You would probably write the first section as the flat-fee portion, the part that has to carry the message on its own. You would treat every subsequent section as a marginal purchase, justified only if it adds something the first section could not. You would cut the transitional paragraph that exists only to move from one idea to the next. You would notice that the second example often does the work the first example already did.

You would also notice something uncomfortable. Some of your best writing might live in the marginal sections — the digressions, the asides, the second thoughts. A per-unit tariff does not just cut fat. It cuts the parts that do not pay for themselves immediately, which is not the same as the parts that do not matter.

This is the real tension the telegram exposes. Per-word pricing produces clarity and economy. It also produces a register that is optimized for the tariff rather than for the reader. The code-word economy is the extreme version: maximum efficiency, minimum voice. The average telegram of 11.93 words is efficient. It is not, as a rule, beautiful.

Inheriting a format versus choosing one

The distinction I keep coming back to is between inheriting a format and choosing one. The telegram sender who wrote in telegraphese was usually choosing, within a constraint. The sender who reached for a code-word was selecting from a menu someone else had built. The newsletter writer who accepts the platform’s default subject line length, default preview text, default send cadence, and default body structure is inheriting a format without seeing its price.

The 1883 Hansard exchange is useful here precisely because it shows the tariff being argued over. Scheme 1 versus Scheme 2. Free addresses versus charged addresses. Sixpence minimum versus sixpence for the first five words. These were not technical details. They were editorial decisions about what kind of message the system would reward.

When you write a newsletter, you are making the same kind of decision, usually without a Hansard transcript to show you the alternatives. The subject line length is a tariff. The preview text is a tariff. The send time is a tariff. The question is not whether you will write inside a priced container. The question is whether you will see the price before you write, or after.

The telegram’s per-word prose is not a template. It is evidence that containers discipline content, and that the discipline is a choice someone made. The writer who wants editorial independence does not need to write in telegraphese. The writer who wants editorial independence needs to know what the container is charging for, and decide whether to pay it.

Frequently asked questions

Was the 1915 telegram rate actually enacted?
The retrieved Hansard record shows a resolution reported and read a second time, then adjourned for further consideration on 12 October. It is a proposed rate, not a confirmed final tariff. I have not found a primary source confirming the enacted rate after that date.

Did email inherit telegraphic style?
The evidence I have does not support that claim. The Wikipedia article on telegram style notes a comparison to text messaging, but the passage is flagged as unsourced. The structural analogy — visible per-unit cost changes prose — is supportable. The lineage claim is not.

What is the average length of a telegram?
A reported figure for US telegrams in the 1900s is 11.93 words, with more than half at ten words or fewer. This comes from a Wikipedia citation to Hochfelder’s The Telegraph in America. I have not verified the underlying study independently.

Where can I see telegram artifacts?
The Postal Museum in the UK holds over 60,000 objects and thousands of records detailing 500 years of postal history, accessible through its online catalogue and highlights pages. I have not confirmed that its holdings include specific telegram artifacts relevant to per-word pricing.

Does per-word pricing always produce better writing?
No. It produces writing optimized for the tariff. That can mean clarity and economy, or it can mean the code-word economy — maximum compression, minimum voice. The tariff is a constraint, not a virtue.

GREETINGS arches over the cat. HUZZ sits beneath it. Between the two words, an orange tabby in a backwards red cap holds a rainbow swirl lollipop in one paw, purple lightning behind it, and stares at you with the flat expression of a creature who has been informed that something is happening and has declined to be impressed. That is the whole design. Two words, one cat, one lollipop, one bolt of purple weather.

I want to argue that this shirt is worth reading closely, not because it is funny — though it is — but because of what it does with the greeting itself. The greeting is the oldest piece of correspondence infrastructure we have. Before the envelope, before the stamp, before the header field, there was a person saying hello to another person and waiting to see what came back. Every format decision in the history of writing to one person descends from that moment. And here, on a cotton shirt, the greeting has been split in two and handed to a cat.

The split salutation

Look at the layout. GREETINGS is not a caption. It is a salutation, doing the work a salutation does: it addresses you, it opens the exchange, it commits the writer to having begun something. HUZZ is not a caption either. HUZZ is the response — an archaic cheer, a word that arrives from somewhere older than the shirt and lands with a thud of mock ceremony. The cat is the third party in the exchange, the one who neither greets nor huzzes but simply is, holding the lollipop, wearing the cap backwards, radiating a small storm.

This is a compressed narrative. It has a speaker, an addressee, and a witness. It has a beginning (GREETINGS) and an end (HUZZ) and a middle (the cat) that refuses to participate in either. If you have ever written a newsletter opening that tried too hard and a sign-off that tried even harder, you know this structure. The salutation commits. The valediction performs. The body is where the actual animal sits, deadpan, holding whatever it is holding.

What the letters are doing

The words are set in blue-purple dimensional letters — the kind of extruded, slightly cartoonish type that reads as announcement rather than label. Dimensional lettering is a specific choice. Flat type would have made the phrase a statement. Dimensional type makes it a sign, something posted, something meant to be seen from across a room. The arch of GREETINGS and the low placement of HUZZ create a frame around the cat, which is the oldest trick in the greeting-card layout: put the message above and below, and let the image carry the meaning in the middle.

The backwards red cap is doing quiet work. A cap worn backwards is a small signal of informality, of not-quite-conforming, of a character who has decided that the conventional orientation is not for them. The rainbow swirl lollipop is the opposite: bright, concentric, almost too cheerful, a piece of candy that looks like it was designed by committee and then handed to a cat who has no intention of eating it. The purple lightning behind the cat adds a third register — mild menace, or mild magic, or just the visual equivalent of a raised eyebrow.

None of these elements explain each other. That is the point. The design is a set of signals that do not resolve into a single message, which is exactly what makes it a meme rather than a slogan. A slogan tells you what to think. A meme gives you the pieces and lets you complete the joke yourself.

The joke is completed by its viewer

This is the part I find genuinely interesting as someone who thinks about correspondence formats. The shirt does not tell a joke. It sets up a joke-shaped space and invites you to fill it. GREETINGS and HUZZ are both greetings, in a sense — one formal, one archaic, one contemporary, one mock-heroic. The cat is neither. The cat is the reader. The cat is you, standing in a room, wearing a shirt that has already said hello and already cheered, while you decide what to do with the lollipop.

That is a different contract from the one most printed humor offers. Most joke shirts deliver a punchline. This one delivers a premise and a witness. The viewer completes it. The viewer is, in the most literal sense, the addressee of the salutation. GREETINGS is addressed to whoever is looking. HUZZ is the response the shirt has already supplied on your behalf. You are not the joke’s audience; you are its second party.

I think that is why the phrase works as a shirt rather than as a caption. A caption explains an image. A salutation addresses a person. This design chose the salutation, and then chose to split it, and then chose to put a cat in the middle who refuses to take sides. The result is a piece of clothing that behaves like a very short letter: it opens, it addresses, it closes, and it leaves the reply to you.

The container and the content

I have spent a lot of time in this column thinking about how containers discipline content — how the 1840 penny post made the letter a mass form, how the 102KB clip made the newsletter a specific shape, how the header field made the mail merge a set of decisions rather than a single act. A t-shirt is a container too, and a strange one. It is a surface that moves. It is read at a glance, from a distance, often while the reader is doing something else. It cannot hold a paragraph. It can hold a salutation and a response and an image, and that is about it.

Given that constraint, the design here is unusually disciplined. It does not try to say too much. It does not stack three jokes. It picks two words that belong to the same family — the greeting — and sets them at opposite ends of the composition, and lets the cat hold the middle. The lollipop and the lightning are not decoration; they are the two possible readings of the cat’s expression. Sweetness and static. Cheer and threat. The viewer picks.

If you are the kind of writer who thinks about salutations — who has ever rewritten the first line of an issue four times because Hi felt too casual and Dear felt too formal and Hello felt like a customer-service email — then you already know the problem this shirt is solving. The greeting is the hardest part of any correspondence. It has to commit without overcommitting. It has to address without presuming. It has to open a door without describing the room.

GREETINGS commits. HUZZ overcommits, on purpose, as a joke. The cat declines to commit at all. That is a complete theory of the salutation, printed on cotton, in two words and one animal.

Reading the object

The shirt is listed as Greetings Huzz Funny Orange Cat Meme Internet Humor from Quirky Cotton Collective. The artwork, as observed on the retail garment image, is exactly what I have described: GREETINGS arched above, HUZZ below, an orange tabby with a backwards red cap, a rainbow swirl lollipop in a paw, purple lightning behind, deadpan expression. I am not going to tell you it is comfortable, or that it fits a certain way, or that people stop you on the street. I have not worn it. I have only read it, which is the appropriate verb for a design that behaves like a very short letter.

What I can tell you is that the design rewards the same kind of attention you would give a well-made salutation. It is not trying to be clever in three registers at once. It is trying to be one thing — a greeting, split in two, with a cat in the middle — and it succeeds because it knows what it is. That is rarer than it sounds. Most printed humor is a caption looking for an image. This is a salutation looking for a reader.

And the reader, if you are wearing it, is whoever is standing in front of you. They get the GREETINGS. They get the HUZZ. They get the cat. The reply is theirs to make.

Editorial note: This publication and Quirky Cotton Collective share an owner.

The garment preview shows it plainly: large, bold, white, lowercase meh. on a dark shirt. No animal. No flourish. No exclamation point hedging the bet. Just four letters and a period, set at a size that would be shouting if the word weren’t so determined not to care.

I want to take that design seriously, which is a slightly ridiculous sentence to write. But the meh shirt is doing something interesting with typography, and typography is the part of writing we notice last and read first. So let’s read it.

Editorial note: this publication and Quirky Cotton Collective share an owner. This is not an independent review.

The period is the whole joke

Strip the period and you have a word. Keep the period and you have a verdict. The lowercase meh is already deflating — it refuses the capital letter that would make it a pronouncement — but the period is what seals it. A period is the punctuation of finality. It says: this sentence is over, and so is the conversation.

Set that period in bold white type at chest scale and you have a contradiction the eye has to resolve. The word says I can’t be bothered. The typography says I went to the trouble of printing this at 72-point. That gap is the design. It’s not a slogan about apathy; it’s a slogan about the effort of performing apathy, which is a much funnier and more honest thing.

I’d call that a compressed narrative. Four characters and one mark of punctuation carry a full arc: the setup (something was expected of me), the turn (I have no strong feelings), the button (and I’m done discussing it). Good short-form writing does this — it trusts the reader to supply the context the words leave out. The shirt trusts you to know what meh means, to hear the flat tone, and to recognize the period as a door closing. If you don’t, the shirt is just a word. If you do, it’s a whole Tuesday afternoon.

Lowercase is a decision, not a default

There’s a whole tradition of lowercase as an aesthetic choice — e.e. cummings, bell hooks, the casual register of the early web — and it usually signals intimacy or refusal of authority. On a shirt, lowercase does something slightly different. It signals that the wearer is not trying to impress you. Capital letters are formal; they stand up straight and make eye contact. Lowercase slouches. Lowercase has already taken its shoes off.

That’s why the design works as a piece of reader address. The shirt isn’t talking to the room; it’s talking past the room, to the one person who gets it. It’s the visual equivalent of a deadpan aside. And the period makes sure you know the aside is finished — no follow-up question, no invitation to chat. The joke is completed by its viewer, not by the wearer. You either read it and laugh inwardly, or you don’t, and either way the shirt has already moved on.

This is the same mechanism as a good footnote, actually. A footnote is a compressed aside that trusts the reader to follow it down the page and back up again. The meh. is a footnote without a referent. It’s the aside itself, printed at the size of a headline.

What the dark ground is doing

The preview shows white lettering on a dark shirt, and that contrast matters. White on dark is high-visibility — it’s the palette of warning labels and night signage. It’s designed to be read across a room. So the shirt is simultaneously saying don’t bother me and you can read this from thirty feet away. That’s the same contradiction as the period, doubled.

I don’t think that’s an accident. The design knows that a shirt is a surface for public text, and it uses the visual grammar of public text — bold, high-contrast, centered — to deliver a private mood. It’s a billboard for a feeling that doesn’t want to be a billboard. That tension is what makes it legible as humor rather than as an actual request for solitude. If it were small and gray, it would just be sad. Large and white, it’s a performance of sadness, which is a different genre entirely.

I should be careful here: I’m describing what I see in the preview, not making a claim about the shirt’s history or its wearers. I haven’t worn it. I don’t know who buys it. I’m reading the artwork the way I’d read a book cover — for the choices the designer made and the effects those choices produce. The observation is the object; the interpretation is mine.

The word that refuses to be a brand

One more thing about meh as a word. It’s a shrug in phonetics — the vowel is flat, the consonant is soft, there’s no plosive to grab onto. It’s the sound of a balloon losing air. That makes it unusually resistant to the usual merchandise treatment. You can’t put meh on a mug with a motivational sunrise behind it. You can’t make it inspirational. The word actively repels the design language of hustle culture, which is probably why it keeps showing up on shirts and not on, say, corporate retreat banners.

That resistance is the useful argument here. A lot of slogan merchandise tries to borrow the authority of a capital letter — BOSS, FOCUS, GRIND — and the all-caps is doing the work of making a small idea feel big. The meh. shirt does the opposite. It takes a small idea and refuses to inflate it, while still using the visual scale of inflation. The result is a joke about the gap between how much we’re supposed to care and how much we actually do.

If you write for a living, you know that gap. You know the feeling of being asked to produce enthusiasm on demand, and you know the specific comedy of answering with a period. The shirt is a small, wearable version of that comedy. It’s not a manifesto. It’s a punctuation mark with a body attached.

Which is, I think, the highest compliment I can pay a piece of typography: it knows exactly how much it needs to say, and it stops.

In 1740, a printer named Samuel Richardson published a novel composed entirely of letters. Pamela, or Virtue Rewarded is not a story about correspondence with letters inserted as decoration. It is a sequence of numbered letters — LETTER I, LETTER II, LETTER III, and so on — and the reader moves through it the way a recipient moves through a mailbag: one bounded unit at a time, each with its own addressee, its own occasion, its own moment of sealing and sending.

That structure is worth examining closely, because it is the same structural question every newsletter writer faces. The container is not neutral. It shapes what can be said, how long it takes to say it, and who is imagined to be listening. Richardson’s novel is a case study in what happens when a writer chooses the container deliberately rather than inheriting whatever the platform provides.

The Printer Who Wrote Letters for a Living

The Project Gutenberg edition of Pamela includes a publisher’s note that explains the book’s origin. Richardson was a printer by trade who rose to be master of the Stationers’ Company. He became a novelist, the note says, “due to his skill as a letter-writer, which brought him, in his fiftieth year, a commission to write a volume of model ‘familiar letters’ as an aid to persons too illiterate to compose their own.”

The note continues: “The notion of connecting these letters by a story which had interested him suggested the plot of ‘Pamela’; and determined its epistolary form — a form which was retained in his later works.”

Read that sequence again. The commission came first. The container — the model letter, the familiar letter, the letter as a teachable form — came first. The story was built to fit it. This is the reverse of how we usually imagine literary invention: not a writer with something to say who then selects a form, but a form already in hand that generates the material.

For anyone who writes into an inbox, that inversion is instructive. Most of us begin with something to say and then pour it into whatever container the platform supplies: a subject line, a preview text, a body field, a send button. Richardson began with the container and discovered what it could hold.

The Letter as a Disciplined Unit

What does the letter form actually discipline? Look at the opening of LETTER I. Pamela writes to her father and mother:

“I have great trouble, and some comfort, to acquaint you with. The trouble is, that my good lady died of the illness I mentioned to you, and left us all much grieved for the loss of her; for she was a dear good lady, and kind to all us her servants.”

The letter has an addressee — two named people, her parents. It has an occasion — the death of her mistress. It has a physical constraint: paper, ink, a hand that can be seen to tremble. Later in the same letter, Pamela describes sealing coins in a pill-box so they will not chink in transit, and hiding the letter in her bosom when her master enters the room. The container is not invisible. It is part of the plot.

Then Mr. B takes the letter from her. “He took it, without saying more, and read it quite through, and then gave it me again.” The private letter has been read by someone other than its intended recipient. The container has been breached, and the breach matters.

This is the first lesson the epistolary novel teaches about serial voice: the writer is always writing to someone specific, but is also aware that the letter may travel further than intended. Pamela writes to her parents. She does not write for Mr. B. But Mr. B reads over her shoulder, and the knowledge of that possibility — not the fact of it, but the possibility — shapes what she writes and how she writes it.

The Double Audience and the Serial Voice

The letters that follow show this negotiation in action. In LETTER II, her parents write back with fear rather than comfort. They worry that she has been “set so above” herself, and they say they would “rather see you all covered with rags, and even follow you to the churchyard, than have it said, a child of ours preferred any worldly conveniences to her virtue.”

In LETTER III, Pamela responds to her father’s letter. She says it has filled her with trouble, that it has made her heart “suspicious and fearful,” and yet she hopes she will never find her master “act unworthy of his character.” The voice here is not a single register. It is intimate — she is writing to her father — and guarded, because she knows the letter may be read by others and because she is trying to manage her parents’ anxiety while managing her own.

This is the condition of the newsletter writer, though the stakes are lower and the pill-boxes are metaphorical. You write to a list. The list is composed of individuals, but it is also a collective, and any individual may forward the issue to someone you did not imagine as a reader. The voice that emerges from that condition is not a single voice. It is a negotiation between the intimacy of the direct address and the exposure of the forwardable artifact.

Richardson’s letters are not optimized for engagement. They are written to specific people for specific reasons, and the variation in length and intensity reflects the variation in occasion. Some letters are short updates. Some are long confessions. The pacing is uneven because the moments being described are uneven. A newsletter that insists on uniform length and tone is applying a platform default — consistency — that may work against the material.

What the Container Does to Pacing

The letters in Pamela are dated and sequential, but they are not uniform. LETTER IV contains a report of Lady Davers’ opinion that Pamela is “too pretty to live in a bachelor’s house,” and a note that Mrs. Jervis said Pamela “was fifteen last February.” LETTER V is a quieter letter about Mrs. Jervis using Pamela “as if she were her own daughter” and taking delight in hearing her read.

The serial rhythm is uneven by design. The writer controls when to send. The reader waits. This is a deliberate format choice, not a platform default. The letter form allows for variation because each letter responds to a specific moment, and moments are not uniform.

Compare that to the default rhythm of a modern newsletter: weekly, or biweekly, or monthly, with roughly consistent length and roughly consistent tone. The consistency is a platform default. It is not necessarily wrong, but it is inherited rather than chosen. The question is whether the consistency serves the material or merely satisfies the calendar.

The Form Was Not Incidental

The publisher’s note in the Gutenberg edition describes Pamela as a novel that “created an epoch in the history of English fiction” and that “marked the transition from the novel of adventure to the novel of character — from the narration of entertaining events to the study of men and of manners, of motives and of sentiments.”

That transition is not separate from the epistolary form. The letter is a container built for character rather than event. It records a voice in a moment, addressing a specific person, responding to a specific situation. The novel of adventure can be narrated from outside. The novel of character, in letters, must be narrated from inside a voice that is always speaking to someone.

Richardson did not invent the epistolary form. The sources do not claim he did. What the sources show is that he was commissioned to write model letters, that the commission led him to connect those letters with a story, and that the form was retained in his later works. The form was the engine, not the ornament.

The Inbox as Editorial Site

For the contemporary writer, the lesson is not “write like Pamela.” The eighteenth-century epistolary novel is evidence, not a destination. The lesson is to notice what the container is doing.

A newsletter is a letter with a list, a subject line, and a send button. The format disciplines the voice. The question is whether you are choosing that discipline or inheriting it.

Consider a practical frame: what would change if you treated each issue as a single letter to a named reader, with a beginning, a middle, and an end, rather than as a broadcast to a segment? The container is the craft. The letter form gives you an addressee, an occasion, a moment of sealing, and a moment of delivery. It gives you permission to vary length and tone because the occasion varies. It gives you a reason to end, because a letter ends.

The inbox is a site of editorial independence only if the writer treats the format as a deliberate choice. Pamela’s letters are not optimized for engagement. They are written to specific people for specific reasons. The container is not invisible. It is the thing that makes the voice possible.

Questions Writers Ask

Was Pamela published serially, in installments?

The retrieved sources do not specify whether Pamela was published in installments or only as a complete volume. The Gutenberg edition presents it as a sequence of numbered letters, and the publisher’s note describes it as a novel published in 1740. The serial structure is internal to the book — the reader experiences the letters in sequence — but the publication history of the volume itself is not established by these sources.

Did Richardson invent the epistolary novel?

The sources do not claim he did. The publisher’s note says the epistolary form was “retained in his later works” and that the novel “created an epoch” and “marked the transition” from adventure to character. Those are claims about influence and formal significance, not about priority or invention.

How many letters are in Pamela?

The table of contents in the Gutenberg edition lists letters up to LETTER XXXII, but the excerpt does not confirm the total number. The novel also includes journal entries, according to the Gutenberg summary, so the letter count is not the whole structural story.

What does this have to do with newsletters?

The connection is structural rather than historical. The letter is a container with an addressee, an occasion, and a physical form. The newsletter is a container with a list, a subject line, and a send button. Both containers discipline the voice that fills them. The epistolary novel is a useful case study because it makes the container visible — the letters are objects that can be hidden, read over a shoulder, or sealed with coins. A newsletter that treats its format as invisible inherits the platform’s defaults instead of choosing its own constraints.

Where can I read Pamela?

The Project Gutenberg edition is available at gutenberg.org/ebooks/6124. The full text is in the public domain in the United States.

Somewhere in your inbox there is a message that begins Dear [FIRST_NAME], or Hi [FIRST_NAME], or — if the platform default has been left untouched — Dear [FIRST_NAME], with the comma sitting outside the bracket like a coat left on the wrong hook. The greeting is the part everyone discusses. It is also the least interesting part of the format.

A merged message has two containers. The first is the body: the paragraphs, the greeting line, the conditional block that says since you’re in [CITY]. The second is the header section, and it is where the rules live. The personalization debate is usually conducted entirely in the first container. The more consequential decisions — who the message claims to be from, whether a reply is possible, how the reader leaves — are made in the second.

The header is a structured container, not free text

RFC 5322, the Internet Message Format specification, defines a message as header fields followed optionally by a body, separated by an empty line. Header fields are lines beginning with a field name, followed by a colon, followed by a field body, terminated by CRLF. That is the whole grammar of the top of your message. It is not a place for prose.

The standard also sets line limits: each line must be no more than 998 characters and should be no more than 78, excluding the CRLF. The conservative 78-character recommendation exists, in the standard’s own words, to accommodate user interfaces that may truncate or wrap the display of longer lines. This is worth sitting with. The limit is not about the wire. It is about the reader’s screen. A long subject line or a long display name is a bet that the client will handle it gracefully. Some do. The standard was written because some do not.

If you are choosing a merge field for a subject line, you are choosing a string that will be concatenated with other strings and then measured against a limit designed for display, not for storage. That is a format decision, and it belongs to you rather than to whatever the platform’s default template happens to do.

From and Sender are an editorial claim

RFC 5322 as updated by RFC 6854 distinguishes two originator fields. The From field specifies the author of the message — the mailbox of the person or system responsible for the writing. The Sender field specifies the agent responsible for the actual transmission. The standard’s example is a secretary sending on behalf of a principal: the principal’s mailbox appears in From, the secretary’s in Sender.

Most merged mail collapses both roles into a single From line. That is a format default, not a requirement. And the standard is explicit about the boundary: From should not contain any mailbox that does not belong to the author or authors of the message.

Read that as an editorial constraint rather than a technicality. A personalized greeting asserts authorship. When a publication merges a first name into the greeting while sending from a shared editorial mailbox, it is making two claims at once — that the message is personal, and that it is authored by the publication. The format permits both. Only one of them is stated in the field the reader sees first. Naming which claim is intended is a craft decision. It is not a deliverability decision, and no amount of subject-line testing will resolve it.

If the writing and the sending genuinely come from different parties — an editor writing under a publication’s name, an assistant sending for a principal — the format already has a field for that. Using it is a deliberate choice. Not using it is also a choice, and it is the one most platforms make for you.

The empty group: a formal option with a cost

The genuinely interesting merge artifact in the retrieved standards is group syntax. RFC 6854 updates RFC 5322 to allow group syntax in the From and Sender fields, as well as in Resent-From and Resent-Sender, in certain situations. The standard’s own example is an automated nightly monitor program, presented like this:

From: Nightly Monitor Robot:;

The empty group after the colon means the message presents itself as coming from a system with no replyable address. Recipients’ email clients will not allow them to reply in the first place. The standard notes that such messages commonly include a valid, replyable address that discards replies — and that recipients who do reply might be unaware their replies will be discarded. The empty group is a way of being honest about that.

It is also a formal option with a cost attached, and the standard says so plainly. Group syntax is characterized as Limited Use. User agents should not permit its use in outgoing messages. Senders need to be aware that using groups in the From field might adversely affect deliverability.

For a writer, this is the most useful kind of artifact: a documented option that most platforms will never offer, with the trade-offs stated in the same document that permits it. You are unlikely to need it. You are more likely to need to know it exists, so that when a platform collapses every originator into a single friendly name, you can see what has been decided on your behalf.

The exit is part of the format

RFC 8058 describes a method for signaling a one-click function for the List-Unsubscribe header field. The requirements are specific. A sender enabling one-click unsubscription places one List-Unsubscribe header field and one List-Unsubscribe-Post header field in the message. The List-Unsubscribe field must contain one HTTPS URI. The List-Unsubscribe-Post header must contain the single key/value pair List-Unsubscribe=One-Click. The message must have a valid DKIM signature covering at least those two headers.

The POST request must not include cookies, HTTP authorization, or any other context information. The sender must not return an HTTPS redirect, because redirected POST actions have historically not worked reliably. And the receiver must not perform the POST without user consent.

Read this as the counterpart to the greeting. The container has a provision for the reader leaving, and that provision is engineered rather than appended. A publication that treats the inbox as a site of editorial independence should treat the reader’s departure with the same deliberateness as the reader’s arrival. The unsubscribe path is not an afterthought bolted onto the format. It is part of the format, and the standard treats it with the same specificity as the address fields.

What the merge actually is

The mail merge is usually told as a story about personalization — a name swapped into a greeting line. The standards suggest a different and more useful account. The merge is a set of decisions about which fields you fill and which you leave honest. Personalization at scale is bounded by the address syntax. The unsubscribe path is bounded by the same header section that carries the greeting.

A hypothetical illustration, clearly labeled as such: a small publication merges a first name into its greeting while sending from a shared editorial mailbox. It is making two claims at once. The format permits both, but only one is stated in the field the reader sees first. Naming which claim is intended is the work. The platform default will not name it for you.

The container disciplines the content. That is not a constraint to work around. It is the material you are working with.

Questions readers ask

Can I use group syntax in my newsletter’s From field? The standard permits it in certain situations, but characterizes it as Limited Use, advises that user agents should not permit it in outgoing messages, and warns that it might adversely affect deliverability. Most newsletter platforms will not expose the option at all. If you need a message that cannot be replied to, the empty group is the documented form; whether it is the right choice for your publication is a separate question.

Does the 78-character line limit apply to my subject line? RFC 5322 states that each line must be no more than 998 characters and should be no more than 78, excluding the CRLF. The recommendation exists to accommodate user interfaces that may truncate or wrap longer lines. Subject lines are not header fields in the same sense, but the reasoning — display, not storage — applies to any string the reader sees first.

What does one-click unsubscribe require? Per RFC 8058: one List-Unsubscribe header with one HTTPS URI, one List-Unsubscribe-Post header containing List-Unsubscribe=One-Click, and a valid DKIM signature covering both headers. The POST must not carry cookies or context information, and the sender must not redirect it.

Should I use Sender if I’m sending from a shared mailbox? The standard distinguishes the author of the message from the agent responsible for transmission, and its example is a secretary sending for a principal. If the writing and the sending genuinely come from different parties, the format has a field for that. Whether your platform exposes it is a separate matter.