An email thread is every message in one conversation, grouped together by the mail client. The first message, each reply and each forward sit in one view, usually with the newest at the bottom. The grouping is done by the client, so the same conversation can look like one thread in Gmail and three in another program.
This guide gives the plain definition, explains how Gmail, Outlook and IMAP mailboxes decide what belongs together, and lists the reasons threads split or merge wrongly. It ends with the habits that keep a thread whole when several people answer from one address, and what a shared inbox adds.
A thread, a chain and a string are the same thing: one conversation's messages shown together. Mail clients group them using the subject and three hidden headers, Message-ID, In-Reply-To and References. A thread splits when one of those changes, which is why a renamed subject or a reply typed as a new message shows up on its own.
What is an email thread?
A thread starts with one message. Every reply to it, and every reply to those replies, carries a hidden reference back to the message it answers. A mail client follows those references and shows the whole set as one item in the list, in order. A thread can be two messages or two hundred.
Email thread vs email chain vs email string
These are three names for one thing. Thread is the term mail clients and documentation use. Chain is common in offices, as in forward me the chain. String and trail turn up in the same sense. Whoever asks for the whole chain wants the thread: every message in the conversation, in order, with nothing cut.
How mail clients group messages into a thread
Every message carries a Message-ID header, a unique string set by the sending software. A reply adds two more. In-Reply-To holds the Message-ID of the message being answered, and References lists every earlier message in the conversation. Clients read these to rebuild the tree, with the subject as a check or a fallback.
| Mail system | Groups by | Known limit | Typical cause of a split |
|---|---|---|---|
| Gmail | Subject without Re: or Fwd:, plus the In-Reply-To and References headers, within a time window | 100 messages per conversation; the next reply starts a new one | An edited subject, or a reply composed as a new message |
| Outlook and Exchange | A conversation index that Outlook writes and each reply extends, plus the subject without prefixes | Sent replies appear only when Show messages from other folders is on | A reply from software that sets no index and changes the subject |
| IMAP mailbox | No thread id in the protocol; the client rebuilds threads from Message-ID, In-Reply-To and References, with the subject as a fallback | Grouping happens per device | A correspondent whose software drops the References header |
Gmail
Gmail calls a thread a conversation. It groups messages that share a subject, ignoring Re: and Fwd:, and that reply to each other through the In-Reply-To and References headers, within a time window. A conversation holds up to 100 messages.
Outlook
Outlook and Exchange use a conversation index. Outlook writes a Thread-Index header when it sends and each reply extends it, so the server can place a message without reading the subject. Mail from other software has no index and is matched on the reply headers and the subject.
IMAP
IMAP is the protocol behind mailboxes at hosting companies and domain registrars, and it has no idea of a thread. A folder is a list of messages. Thunderbird, Apple Mail and every other client rebuild threads on the device from the headers, so two clients can group the same folder differently.
Why email threads split
A split is one conversation shown as two or more threads. Each cause below breaks one of the keys a client relies on.
- The subject was edited. Someone adds a date or an order number while replying. Gmail treats the new subject as a new conversation, and IMAP clients that fall back on subject do the same.
- A reply was sent as a new message. The sender pastes the address into a fresh compose window instead of pressing Reply, so no header links it to the original.
- The other side's software drops References. Some ticketing systems, web forms and CRM senders reply without the headers. Gmail and Outlook can still match on subject. An IMAP client has nothing left if the subject changed too.
- A forward went to someone new. A forward is a new message with its own Message-ID, so the recipient's reply points at the forward. Some clients file it under the original thread and others start a second one.
- A different address replied. A teammate answers from their own mailbox instead of the shared one, so the shared thread is missing a message the client has seen.
- The thread hit a cap. Gmail starts a new conversation after 100 messages.
Why threads merge when they should not
The opposite failure is a thread that holds two conversations, and short subjects are the usual cause. A client who sends Invoice every month from billing software that sets no reply headers can end up in one long thread, because subject and sender match. In an IMAP client with subject fallback, three customers writing Hello can land in one group.
The fix sits with the sender. A subject that names the job, such as Invoice 2041 for October, gives every client a unique key.
Email thread etiquette for a team
Reply all with care
Reply keeps the conversation between you and the sender. Reply all keeps everyone who was copied. Dropping someone without saying so is how a client misses a decision, and adding a crowd is how a thread becomes noise. Check To and Cc before you press either.
Change the subject on purpose
A subject change splits the thread in Gmail and in subject-based clients. Do it only when the topic has changed, and say so in the first line: starting a new thread for the contract renewal. Otherwise leave the subject alone, even if the original was badly worded.
Know when to start a new thread
Start a new thread when the question is new, when the people are different, or when the old thread is too long to search. Keep replying in the thread when the question is the same, because the history travels with it.
Trim the quoted text
Each reply quotes everything below it, so a thirty-message thread carries thirty copies of the opening. Trim the quote to the part you are answering when you change topic or add people. Leave it whole when a client may need the history, since the quote is all a forward carries.
How to start an email thread
Write a subject that will still work as a key in six months: the client, the job and the thing being decided. Put the people who need to act in To and the people who need to know in Cc. Keep one topic per thread.
How to find a whole email thread
- In Gmail, open any message in the conversation and the rest is already there. If conversation view is off, search the subject in quotes, or use the rfc822msgid: operator with a Message-ID copied from Show original.
- In Outlook, right-click a message, choose Find Related, then Messages in this Conversation. Turn on Show messages from other folders so your own sent replies appear.
- In an IMAP client, turn on threaded view for the folder and sort by date. Search the subject, then the sender.
- In a shared inbox, search the client's name or the subject and the thread comes back as one record.
What a shared inbox adds to a thread
A mail client groups messages. A shared inbox turns the group into a record the team works from. Each thread has an owner, internal notes and a history of who replied and when the state changed. Splits matter more here, because a split thread can end up with two owners and two sets of notes.
Where Sektra fits
We build Sektra, an AI shared inbox for client teams. Gmail and Outlook mailboxes keep their native grouping, so one thread in Gmail is one thread in Sektra. For IMAP mailboxes, Sektra builds threads from the Message-ID, In-Reply-To and References headers, since IMAP supplies no thread id. A correspondent whose software drops those headers can still split a conversation, as in any client.
Every thread has an owner, notes the client never sees and a history of who did what. The assistant answers questions about a client with the threads it drew on linked. Sending stays with a person: the assistant drafts, a teammate reviews and sends. The feature reference is on /product.
A thread is only as whole as the headers that reach it. Keep subjects stable, press Reply instead of composing fresh, and answer from the mailbox the conversation lives in. Those three habits prevent the common splits.
