What changes when you reply?

When you hit reply, your email client creates a completely new message with its own unique Message ID. It's not the same message coming back. It's a fresh send that happens to reference the original.

Here's what changes under the hood:

• In-Reply-To header: Gets set to the Message ID of the email you're replying to. This tells threading systems "this message is responding to that one."
• References header: Gets updated with the full conversation chain. If you're replying to a reply to a reply, all those Message IDs stack up in References.
• Subject line: Gains a "Re:" prefix (short for "regarding" or "reply", depending on who you ask). Most clients add this automatically.
• Body: Quotes the original message, usually prefixed with "On [date], [sender] wrote:" or similar.

The threading headers (In-Reply-To and References) are what let Gmail, Outlook, and other clients group conversations together. Without them, your reply shows up as a brand new thread.

But here's the critical part for deliverability: mailbox providers treat your reply as a completely new message. It gets its own SPF, DKIM, and DMARC check. The thread history helps with organization, but each message in the conversation is evaluated on its own authentication and reputation. If your reply fails DMARC, it can still land in spam even if the original message you're replying to made it to the inbox just fine.

This matters more than you'd think. If you're replying from a domain with broken authentication (say, you're using a personal Gmail address to reply to a work conversation, or your company's DMARC policy is set to reject), your reply might not deliver even though you're just continuing an existing thread.

Want to see what headers your email client actually adds when you reply? Use our free Email Header Analyzer to check In-Reply-To, References, and authentication results on any message.