Understanding Email Threading & Replies

Email threading in AliasFleet is the grouping of forwarded mail and replies into one conversation in Gmail, Apple Mail, and Outlook. The page covers the headers that link messages, the inbound reply flow, starting a new conversation, and the checks that fix a split thread.

How do email clients group messages into a thread?#

Gmail, Apple Mail, and Outlook place messages in one thread when two conditions are met: the reply carries headers that reference earlier messages in the chain, and the subject matches apart from prefixes such as Re: and Fwd:. When both conditions are met, the client displays the full exchange as a single conversation. When either condition is not met, the client opens a separate thread.

The grouping mechanism is defined by RFC 5322. Each message carries a unique Message-ID header. A reply adds two headers that reference earlier messages in the chain, and AliasFleet preserves both headers on forwarded mail and on replies, so clients can rebuild the chain.

Subject matching works on the base subject. The client ignores Re: and Fwd: prefixes and compares the remaining text, so a reply with an unchanged subject remains in the thread while a reply with a rewritten subject does not.

What happens when a message arrives at an alias?#

Most alias communication begins when a service, newsletter, or contact emails an alias address. The inbound reply flow runs as follows:

1. Inbound delivery. The email arrives at alias@yourdomain.com. AliasFleet forwards it to the destination inbox with an encoded Reply-To header, for example alias+sender=company.com@yourdomain.com.
2. Thread creation. The email client builds the conversation thread in the inbox from this first message.
3. Reply. Clicking Reply in the email client attaches the In-Reply-To and References headers and sends the response to the encoded address.
4. Outbound dispatch. AliasFleet checks the destination permissions, replaces the personal email address with the alias identity, and delivers the reply.
5. Continued grouping. When the contact replies again, the incoming email sits inside the existing inbox thread, and later exchanges remain grouped in the same thread.

How does a new conversation start from an alias?#

A new conversation starts when the alias holder contacts someone first, rather than answering a forwarded message. Two methods start a new conversation:

1. Use the in-app Quick Send composer. Select the alias in the dashboard, compose the message, and send it. Optional attachments and custom display names are available in the composer.
2. Use the relay address from a mail app. Send an email to alias+recipient=domain.com@yourdomain.com, where the alias and the recipient domain match the intended conversation.

In both cases, AliasFleet assigns a clean domain Message-ID to the outbound email, so no originating identifiers from the personal mail provider enter the message. In the recipient inbox, the thread begins with this first message. When the recipient replies, the conversation thread opens in the destination inbox, and all later replies remain grouped in that thread. The full steps for both methods are covered in Send from Aliases.

How are replies protected in transit?#

Every forwarded email and outbound reply routed through AliasFleet carries three mechanisms that keep authentication intact across forwarding:

• RFC 6376 section 8.15 DKIM oversigning. Signing covers headers that a downstream relay could otherwise add or alter, which guards against downstream spoofing and header injection.
• RFC 8617 ARC sealing. Authenticated Received Chain sealing preserves upstream authentication results across multi-hop relays, so a forwarder in the chain does not break the authentication record.
• SRS (Sender Rewriting Scheme). Rewriting the sender envelope keeps SPF alignment intact when mail passes across external mail providers.

These mechanisms operate on every forwarded message and reply. They do not change how the thread appears in the client, and they do not expose the personal address, IP address, or origin headers in the sent message.

What keeps threads intact?#

Three practices keep conversation history in one thread:

• Leave reply subjects at the default. Keep custom subject overrides disabled for replies (use_reply_subject = false). Retaining the standard Re: <Original Subject> header means mail clients do not branch the conversation into separate threads.
• Reply to the forwarded message. Always click Reply directly on the forwarded message rather than composing a new, standalone email to the sender. A new compose carries no In-Reply-To header, so the client cannot attach it to the existing thread.
• Use Quick Send for new topics. When starting a new topic from scratch, use the dashboard Quick Send feature to select the alias and compose the message, rather than replying to an unrelated thread.

How is a split thread checked?#

Verification takes one test exchange. Send a reply to a forwarded message, then confirm in the destination inbox that the reply sits under the original thread, and confirm that the sent reply shows the alias address rather than the real address. If the reply appears as a separate conversation, work through the following checks in order:

If every check above passes and the thread still splits, the cause sits outside AliasFleet threading: the other party changed the subject, or their client groups by subject only and treats the exchange as separate. In that case the thread cannot be rejoined from the AliasFleet side, and the conversation continues from the newest message.

Related guides#

• Reply from Aliases: enabling Can Reply and replying to forwarded mail from an alias.
• Send from Aliases: starting new conversations from an alias with Quick Send or the relay address.
• How Email Aliases Actually Work: everyday examples of one alias per site, and how forwarding to a destination inbox works.