Email course glossary

Alignment

Also called DMARC alignment, identifier alignment.

Alignment is the DMARC requirement that the domain a reader sees in the From header match a domain that passed SPF or DKIM, which is why a message can pass both of those checks and still fail DMARC.

Mail passes SPF and passes DKIM and fails DMARC when both passes were on the sending provider’s domain while the From line said yours. That is the default state with a good many sending services until the domain setup is finished, and it looks identical to success everywhere except in a DMARC aggregate report.

SPF aligns on the envelope sender, the address bounces are returned to, and DKIM aligns on the domain named in the signature. Only one of the two has to align for DMARC to pass, and relaxed alignment accepts a subdomain of the same organisational domain, which is why sending from a subdomain reserved for mail breaks nothing.

Bulk sender requirements

Also called Google and Yahoo sender requirements, Outlook.com sender requirements, February 2024 email requirements.

The bulk sender requirements are the rules Google and Yahoo have enforced since February 2024, and Outlook.com since May 2025, on high-volume senders: SPF and DKIM both passing, DMARC aligned with the From domain, and, at Google and Yahoo, one-click unsubscribe and a spam complaint rate under 0.3 per cent.

Call to action

Also called CTA.

A call to action is the single thing an email asks the reader to do, stated plainly and linked once, which in a course email is usually the step that day’s lesson was teaching rather than a request to buy anything.

One per email is the working rule. A message with three asks is a message with none taken, and in a teaching sequence the ask is also the measurement, because a click on a link that a reader who actually did the thing has a reason to press is the only progress signal worth counting.

Put the link where it belongs in the teaching, on a worksheet, the next step or a reply prompt, rather than at the bottom as a read-more. A course can afford a plain ask: the reader confirmed their address for this, and the sequence is the reason the message is in front of them.

Completion rate

A completion rate is the share of confirmed subscribers who reach the end of a course, and for a five-day course measured by a click on the last day it commonly runs between one in ten and one in four, with longer courses lower.

Confirmed opt-in

Also called double opt-in, DOI.

Confirmed opt-in, usually called double opt-in, is the practice of sending one message to a newly submitted address and adding it to a list only after somebody clicks the link in that message.

Consent record

Also called proof of consent.

A consent record is the evidence that a particular person agreed to receive a particular kind of mail, kept because Article 7(1) of the GDPR puts the burden of demonstrating consent on whoever relies on it.

What to keep is what you would need in order to answer a complaint a year later: what the person was shown, what they agreed to, when, and from where. A timestamp and an address on their own describe a row in a table rather than an act by a person.

A confirmation click is the cheapest version of this, because it is a timestamped act performed at the address itself. The GDPR names no mechanism and does not contain the phrase double opt-in; it defines consent as freely given, specific, informed and unambiguous in Article 4(11), and leaves the evidence to you.

Deliverability

Also called inbox placement.

Deliverability is the share of the mail you send that reaches the inbox of the person you addressed it to, as distinct from delivery, which is only the share the receiving server accepted rather than bounced.

A message can be delivered and never seen: accepted at the door, filed straight into the spam folder, counted as a success by the sending side and read by nobody. The receiving provider does not report which folder it chose and will not, which is why deliverability is inferred from complaint rates, bounces and behaviour rather than read off a dashboard.

For a small sender it comes down to authenticated mail on a domain you control, a spam complaint rate under the level the large providers enforce, hard bounces suppressed on the first failure, and a list that confirmed it wanted the mail.

Delivery rate

Also called accepted rate.

A delivery rate is the share of a send that the receiving mail server accepted instead of bouncing, and it says nothing at all about whether any of it reached an inbox.

It is the number a sending dashboard can actually see, which is why it is the number sending dashboards show. Ninety-nine per cent delivered is entirely compatible with every message sitting in a spam folder, so a sender can look healthy on their own reports for months while their mail quietly stops arriving anywhere a person looks.

The useful thing to do with it is watch it move rather than admire it. A drop means bounces, and a jump in bounces means either a list nobody confirmed or a suppression list that is not being applied before the send.

Disposable email domain

Also called throwaway address, temporary email.

A disposable email domain is one that hands out addresses which expire or forward nowhere after a short period, typed by people who want the thing being offered without the mail that comes with it.

They are not a deliverability disaster in themselves, because a confirmation step removes most of them for free: an address nobody intends to read is an address nobody clicks a link at. What they cost is list size that was never real, and a completion rate calculated against people who were never there.

Blocking them by name is a maintenance job with no end, since the list of such domains changes weekly and every blocklist catches ordinary providers by accident. Confirmation is the cheaper control and it needs no list.

DKIM

Also called DomainKeys Identified Mail.

DKIM is a cryptographic signature over a message’s headers and body, made with a private key held by whoever sends the mail and checked by the receiver against a public key published in DNS under a selector, and it is defined in RFC 6376.

DMARC

Also called Domain-based Message Authentication, Reporting and Conformance.

DMARC is the DNS policy that ties SPF and DKIM to the domain a reader actually sees, telling receivers what to do with mail from your domain that aligns with neither and asking for aggregate reports about it, and it is defined in RFC 7489.

The record lives at _dmarc under your domain, and its policy tag is the point of it: none means report what is happening and deliver it anyway, quarantine means treat failures as suspicious, and reject means refuse them. A domain that sends no mail at all should publish a reject policy, which is the cheapest anti-impersonation measure available to anybody who owns a domain.

A policy of none is the right place to start and the wrong place to stay. Its purpose is to collect aggregate reports for a few weeks so you can find the legitimate senders you had forgotten about and fix their authentication; a domain that has been on none for three years has a record that satisfies the bulk sender requirement and has never once caused a forged message to be refused.

Domain warming

Also called IP warming, warm-up.

Domain warming is the practice of raising the volume sent from a new domain gradually, over something like two to four weeks, so that a domain with no reputation does not arrive looking like one registered this morning for a campaign.

Neither Google nor Yahoo publishes a ramp; Google says only to start low, increase slowly and watch the signals, and Yahoo says nothing about volume at all, so anyone quoting a schedule to three decimal places is quoting a habit. The shape most senders use is a few hundred messages a day to the addresses most likely to engage, held for two or three days, then roughly doubling every two to three days while complaint and soft bounce rates stay flat.

If a rate moves you hold rather than push through. A course sender gets part of this for free, because a course fans out one message per subscriber per day rather than one blast to everybody at once.

Drip campaign

Also called automation sequence, autoresponder.

A drip campaign is a stored sequence of emails sent to a person on a timer after some trigger, run towards a goal the sender chose, which is the same machinery an email course runs on and a different promise to the reader.

Email course

Also called email mini-course, course by email.

An email course is a finite sequence of five to ten lessons delivered one email at a time, in order, on a clock that starts when each reader joins, and it ends on a day both of you knew about in advance.

Evergreen and cohort courses

Also called evergreen course, cohort course.

An evergreen course starts when each person confirms and is therefore running continuously, while a cohort course starts on one fixed date for everybody, so nobody in an evergreen course is ever late and nobody in a cohort is ever alone.

Both work, and the choice is between a shared moment and a thing that keeps working while you do not. A cohort earns its cost when the shared moment genuinely adds something, which in practice means a live element, a group, or a leaderboard that only makes sense if everybody is on the same day.

The usual mistake is running a cohort because a launch feels like an event. Absent a live element, a cohort is a deadline you have imposed on yourself, and every reader who finds the page the day after it starts is asked to wait or to leave.

Feedback loop

Also called FBL, complaint feedback loop.

A feedback loop is an arrangement in which a mailbox provider reports back to a sender the messages its users marked as spam, so that those addresses can be suppressed immediately rather than mailed again.

Not every provider offers one and the terms differ: some report the complaint with the address and some strip it, and Gmail runs no per-message loop of the ordinary kind at all, offering aggregate rates in its postmaster dashboard instead. Most sending platforms enrol in the loops that exist and act on them without being asked.

What a loop is for is the one thing worse than a complaint, which is a second message to somebody who already complained. An address that arrives through a feedback loop belongs on the suppression list the same day, and it never comes back off it.

Five-day challenge

Also called 5-day challenge.

A five-day challenge is five daily emails that each ask the reader to do one small thing, usually framed by a pre-challenge email before day one and an offer on day six, which makes seven, so the unit of progress is an action rather than a lesson.

Hard bounce

A hard bounce is a permanent refusal of a message by the receiving server, carried in a 5xx SMTP response, because the mailbox does not exist, the domain does not exist, or the address has been disabled.

It must be suppressed immediately and permanently, on the first occurrence, not after three and not after a review. Continuing to send to an address you have been told does not exist is the clearest signal available to a receiving provider that a sender does not process its bounces, and not processing bounces is the operational signature of a bought or scraped list.

It is also how you keep mailing a spam trap, which is an address that exists only to be mailed by people who should not have it. A confirmation step removes most of the addresses that would hard bounce before they are ever sent to a second time.

Lead magnet

Also called opt-in incentive, freebie.

A lead magnet is a specific, useful thing offered in exchange for an email address and permission to send more, and both halves matter: without the useful thing you are asking a stranger for their address for nothing, and without the permission you have a download page and no list.

List hygiene

Also called list cleaning, sunsetting.

List hygiene is the work of keeping a list to addresses that exist and belong to people who still want the mail: hard bounces suppressed on the first failure, long-silent addresses retired, typos caught at the form, and nothing re-imported that was already suppressed.

The sunset window is the part that needs a number, and the honest answer is a range: most senders stop after somewhere between three and six months with no measurable engagement. A course sender can be stricter than a newsletter, because a course either gets finished or it does not.

What matters more than the exact window is that there is one and that it applies automatically. Hygiene done by hand is hygiene done when somebody remembers, which is after the complaint rate has already moved.

List-Unsubscribe

List-Unsubscribe is a message header offering machine-readable ways out of a list, and paired with a List-Unsubscribe-Post header carrying the value List-Unsubscribe=One-Click it is what a mail client uses to unsubscribe a reader without opening a browser.

Two headers do the work and one-click requires both. List-Unsubscribe on its own predates RFC 8058 and offers exits a client may choose to present; List-Unsubscribe-Post is the header that declares the https URI safe to POST to without asking the reader anything further. A message with the first and not the second does not have one-click unsubscribe, whatever the sending dashboard says.

The header value usually carries two exits in angle brackets, an https URI and a mailto. The https one is what one-click uses, and the mailto is the fallback for clients that prefer it.

Mail Privacy Protection

Also called MPP, Apple Mail Privacy Protection.

Mail Privacy Protection is the Apple Mail feature that loads a message’s remote content through a proxy whether or not the reader opened it, which is what stopped an open rate from measuring anything about a person.

One-click unsubscribe

Also called RFC 8058 unsubscribe, 1-click unsubscribe, List-Unsubscribe-Post.

One-click unsubscribe is a mail client operating the unsubscribe on the reader’s behalf by POSTing to an https URI the sender put in the message headers, with no browser, no confirmation page and no further interaction from the reader, as RFC 8058 defines it.

Open rate

An open rate is the share of delivered messages in which a tiny remote image loaded, used as a proxy for a human having looked, and it is unreliable because that image is fetched by proxies and caches that are not readers and never fetched by clients that block images.

The false positives and the false negatives arrive in proportions that differ by provider and change without notice. Gmail fetches and caches remote images through its own servers, Apple Mail Privacy Protection fetches them on the reader’s behalf whether or not the message was opened, and any client with images off registers nothing at all.

A sender who prunes a list by open rate is therefore pruning partly at random. There is a second objection with nothing to do with accuracy: the pixel puts a third-party host and a remote image load into every message, and an invisible image reporting a reader’s behaviour is processing personal data that has to be disclosed and justified like any other.

Opt-in page

Also called landing page, sign-up page, squeeze page.

An opt-in page is a page whose only job is to describe one thing and collect an email address for it, and a dedicated one is planned at 15 to 30 per cent of its visitors where an inline form in a sidebar converts 1 to 3 per cent.

The difference is not persuasion, it is that the page has one subject and one field. A visitor who arrived for the thing being offered is asked for one decision, and everything else on the page is either evidence for that decision or in the way of it.

Say what arrives, how many days it runs and what happens next, because the sentence on this page sets the expectation the confirmation email then has to meet. A reader who does not recognise what they signed up for eleven seconds later is where a complaint comes from.

Preheader

Also called preview text, preheader text.

A preheader is the line of text an inbox shows after the subject when there is room, taken from the top of the message body, and it is a separate opportunity rather than an extension of the subject line.

On a phone it is often the line that decides, and left unset it fills with whatever the email happens to begin with, which is frequently a logo alt text or the words “View this email in your browser”.

Writing it is close to free and almost nobody does it. In a course it is the natural home for the day number, on the mornings when the subject line needs its whole width for something more interesting.

Re-permission campaign

Also called reconfirmation campaign, permission pass.

A re-permission campaign is a single message sent to an existing list asking the people on it to confirm that they still want the mail, after which everybody who did not confirm is suppressed rather than mailed again.

It is what you run when you cannot show how a list was collected, when it has been silent for a long time, or when it arrives with a business you acquired. It is expensive in list size, and it is the only way to turn a list you cannot account for into one you can.

The message has to stand on its own, because most of the people receiving it do not remember you. Name the thing they signed up for, say when and where if you know, say what happens if they do nothing, and ask for exactly one click.

Send it in batches rather than all at once. A large send to a list with a poor complaint rate is the send that damages the domain you were trying to rescue.

Role address

Also called role account, generic address.

A role address is one that belongs to a function rather than to a person, of the info, support or sales kind, and it is read by several people, by nobody, or by a ticket system.

Mailing one is riskier than mailing a person for two reasons. Nobody at a shared mailbox has personally agreed to anything, so a complaint is likelier; and several of the addresses used as spam traps are role addresses, precisely because a role address that never signed up for anything is a good way to catch a sender who did not ask.

A confirmation step settles this without a blocklist. Somebody has to open the mailbox and click, which is exactly the evidence a role address otherwise cannot give you.

Seed list

Also called seed testing, inbox placement test.

A seed list is a set of addresses you control at several mailbox providers, mailed alongside a real send so that you can open each account yourself and see which folder the message landed in.

It exists because no provider reports inbox placement back to a sender, so the only way to observe the difference between delivery and deliverability is to be the recipient. A handful of accounts at the providers your readers actually use tells you more than any score a tool will sell you.

Treat the result as an indication rather than a measurement. Seed accounts have no reading history, no contacts and no engagement, and filtering is personalised, so a message that reaches a seed inbox can still be filtered for a reader who has never opened one of yours.

Sender reputation

Also called domain reputation, IP reputation.

Sender reputation is what a mailbox provider has learned about the domain and the infrastructure your mail comes from, assembled from complaints, bounces, spam trap hits and how the people who receive your mail behave, and it is what decides the folder.

It is held per provider and it is not portable: Gmail knows nothing about what Yahoo thinks of you. Nobody publishes the function, and the only window most senders get is the provider’s own postmaster dashboard, which is free to whoever proves they control the domain.

Now that authentication is a floor, the identity carrying reputation is the domain in your DKIM signature rather than an IP address. That is the argument for sending from a subdomain reserved for mail: a burned subdomain can be retired in an afternoon, and a burned root domain takes your invoices and your password resets with it.

Sending domain

A sending domain is the domain that signs and sends your mail, and it is worth separating from the sending infrastructure: the IP addresses mail leaves from are shared by default at every provider serving small senders, while the domain in the signature and the From line is yours alone.

The decision that matters for a small sender is therefore not shared against dedicated IP addresses. IP reputation is built by sustained volume, and a dedicated IP under a low-volume sender is an IP with no reputation at all, which is worse than a share of a well-run pool.

What there is to decide is which of your domains does the sending. Use a subdomain reserved for it and keep the root domain for the mail humans send each other, because a burned subdomain can be replaced in an afternoon and a burned root domain cannot be replaced at all.

Single opt-in

Also called SOI.

Single opt-in means an address starts receiving mail as soon as it is typed into a form, with nothing in between to establish that the person who typed it owns the mailbox it points at.

Its advantage is real and it is the reason it persists: nobody is lost between the form and the list. Its cost is that an email form accepts any string shaped like an address, so a share of what arrives is a typo, a colleague, somebody who wanted the download and not the mail, or a bot.

From a mailbox provider’s point of view every one of those is indistinguishable from a bought list. They bounce, or they sit and never engage, or they press the spam button, and all three are measured against you.

Soft bounce

A soft bounce is a temporary refusal of a message by the receiving server, carried in a 4xx SMTP response, because the mailbox is full, the server is greylisting you, or you are being rate-limited.

It is retried with backoff rather than suppressed, and reclassified if it keeps happening. There is no published figure for when a soft bounce becomes permanent, because it depends on the reason code, but a common shape is to retry over a day or two and then treat somewhere between three and seven consecutive soft failures across a week or two as a hard bounce.

A mailbox that has been full for a fortnight is not a reader. A rise in soft bounces at one provider and nowhere else is also worth reading as a message about you rather than about the mailboxes, because that is what throttling looks like from the sending side.

Soft opt-in

Also called existing customer exemption.

The soft opt-in is the narrow exception in European electronic marketing rules that lets a seller market its own similar products to somebody whose details were obtained in the course of a sale, provided that person was given a clear chance to object when the details were collected and in every message since.

Spam complaint rate

Also called complaint rate, abuse rate.

A spam complaint rate is the count of people who pressed the spam or junk button divided by the mail delivered to that provider over a window it chooses, and both Google and Yahoo name 0.3 per cent as the level to stay under, with Google naming 0.1 per cent as the level to aim at.

SPF

Also called Sender Policy Framework.

SPF is a DNS record listing the servers allowed to send mail for a domain, checked by the receiver against the envelope sender rather than against the From line a reader sees, and it is defined in RFC 7208.

Subject line

A subject line is the line an inbox shows beside your name, and the length that matters is not the total but the front of it: put what is interesting in the first 30 to 40 characters, which is roughly what an iPhone held upright will show.

An inbox truncates at a pixel width in a proportional typeface rather than at a character count, so every figure quoted in characters is a translation that moves with the letters you chose. Outlook on a desktop shows roughly 60 and Gmail in a wide browser window roughly 70, and the shortest of the three is your working budget, because it is the one your reader is most likely holding.

A course subject line does not have to sell anything, which is a freedom worth using. The reader confirmed their address for this and the sequence is the reason the message is there, so a plain description of the day beats anything clever, and a “Day 2 of 5:” prefix costs about eleven characters for a real gain in orientation.

Suppression list

Also called do-not-mail list, exclusion list.

A suppression list is the permanent record of addresses that must never be mailed again, holding unsubscribes, complaints and hard bounces, and it is checked before every send rather than after one.

It is the most valuable list you own and the one most often lost. It has to survive every re-import, every change of sending platform and every export to a spreadsheet, because the way somebody gets mailed after they left is almost always a list that went around a suppression check rather than through it.

When somebody exercises a right to erasure you still need to not mail them again, which is the apparent contradiction at the centre of this. It is usually resolved by keeping the minimum necessary to honour the request rather than the record itself: a one-way hash of the normalised address, with no name, no history and no profile attached, so what is retained is a prohibition rather than a subscriber.

Unsubscribe

Also called opt-out.

An unsubscribe is a reader withdrawing permission to be mailed, and since February 2024 Google and Yahoo have required one to be honoured within two days, a much shorter clock than the 10 business days the United States CAN-SPAM Act allows.

Two days is the outer limit and there is no reason to use it. An unsubscribe is a single row and the send is asynchronous, so the honest implementation removes the address before it answers the request; the senders who need the two days are the ones running an export to a spreadsheet and an import back, which is also how somebody gets mailed after they left.

Every commercial email carries two exits: the headers, for clients that can operate them, and a visible link in the body for everybody else. The link is not optional, because not every client renders an unsubscribe control, a forwarded message loses it entirely, and CAN-SPAM requires a clear and conspicuous explanation in the message itself.

A message that arrives after somebody asked to leave does not produce a second unsubscribe. It produces a spam button press from a reader who now believes you ignored them, and those are the complaints that move a complaint rate fastest.

Welcome sequence

Also called welcome series, onboarding emails.

A welcome sequence is the short run of emails a new subscriber receives after joining a list, sent to introduce who you are and what will arrive, and it is the mail people are most likely to read because it is the only mail they are expecting.

It differs from a course in what it is for. A course teaches something and ends on a day the reader was told about; a welcome sequence sets an expectation for an ongoing arrangement, so it can be two messages or five and it has no natural last day of its own.

The first message is the one that matters, because it arrives while the reader still remembers signing up. Name the thing they asked for, say what arrives and when, and key the sequence to the moment they joined rather than to a date on your calendar.