Understanding Email Threading & Replies

When communicating through email aliases, you want conversation history to stay organized in standard email clients (such as Gmail, Apple Mail, and Microsoft Outlook) without leaking your real email address or personal server headers.

This guide explains how conversation threading works in AliasFleet and best practices for keeping your inbox organized.

How Email Clients Group Conversations

Modern email clients use the standard RFC 5322 protocol to group messages into unified conversation threads based on two key elements:

1. Header References (In-Reply-To & References): Each reply references the unique Message-ID of the previous email in the chain.
2. Subject Line Matching: The base topic of the subject (ignoring Re: and Fwd:) must match.

When both conditions match, your email client automatically collapses all incoming and outgoing messages into a single, easy-to-read thread.

The Inbound & Reply Flow (95% of Use Cases)

Most alias communication begins when a service, newsletter, or client emails your alias address:

1. Inbound Delivery: The email arrives at alias@yourdomain.com. AliasFleet forwards it to your real inbox with an encoded Reply-To header (e.g., alias+sender=company.com@yourdomain.com).
2. First Thread Started: Your email client creates the conversation thread in your Inbox from Message #1.
3. 1-Click Reply: When you click Reply in your email client, your client includes In-Reply-To and sends your response to the encoded address.
4. Outbound Dispatch: AliasFleet verifies your destination permissions, replaces your personal email with your alias identity, and delivers the reply.
5. Continuous Grouping: When the contact replies back, the incoming email nests seamlessly inside your existing inbox thread.

Outbound New Sends (Initiating Contact)

When you initiate contact with a new person using your alias (either via the in-app Quick Send composer or by emailing alias+recipient=domain.com@yourdomain.com):

• Privacy Protection: To prevent your personal mail provider's originating identifiers from leaking, AliasFleet assigns a clean domain Message-ID on the outbound email.
• Recipient View: In the recipient's inbox, the thread begins immediately from your first message.
• Your Inbox View: When the recipient replies, the active conversation thread opens in your Inbox, and all subsequent replies back and forth remain permanently grouped in that thread.

Best Practices for Clean Threading

To ensure your email client never fragments conversation history:

1. Leave Reply Subjects Default

Keep custom subject overrides disabled for replies (use_reply_subject = false). By retaining standard Re: <Original Subject> headers, mail clients will never branch the conversation into separate threads.

2. Reply to the Forwarded Message

Always click Reply directly on the forwarded notification rather than composing a new, standalone email to the sender. This ensures your email client attaches the correct In-Reply-To headers.

3. Use Quick Send for New Outbound Conversations

When starting a brand new topic from scratch, use the dashboard Quick Send feature to select your alias and compose your message with optional attachments and custom display names.

Cryptographic Deliverability & Privacy

Every forwarded email and outbound reply routed through AliasFleet includes:

• RFC 6376 §8.15 DKIM Oversigning: Protects against downstream spoofing and header injection.
• RFC 8617 ARC Sealing: Preserves upstream authentication across multi-hop relays.
• SRS (Sender Rewriting Scheme): Maintains SPF alignment across external mail providers.