What is the “In-Reply-To” header?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

The In-Reply-To header is what tells an email client "this message is a reply to that specific email over there." It does this by referencing the Message-ID of the email you're replying to. Without it, your reply just looks like a brand new email, and the conversation thread falls apart.

When you hit "Reply" in Gmail, Outlook, or any mail client, it automatically adds an In-Reply-To header with the Message-ID of the email you're responding to. That's how the client knows to show your reply underneath the original message in a threaded view instead of scattering it somewhere else in the inbox.

Here's what an In-Reply-To header looks like in the raw email source:

In-Reply-To: <abc123@harbor.post.net>

That <abc123@harbor.post.net> is the Message-ID of the email you replied to. Your mail client uses that ID to link the two messages together visually.

For most people, this is completely automatic and invisible. You don't set it manually. Your email client or ESP handles it when you hit reply. But if you're building your own email sending system or debugging why threads aren't working, the In-Reply-To header is what you need to check.

When threading breaks (your reply shows up as a new message instead of in the conversation), it's usually because:

  • The In-Reply-To header is missing entirely
  • The In-Reply-To header references a Message-ID that doesn't match the original email
  • The original email never had a Message-ID in the first place
  • The Subject line changed too much (some clients use Subject matching as a fallback)

If you're building transactional emails that people might reply to (support tickets, order confirmations, shipping updates), make sure your ESP or mail server is setting In-Reply-To correctly when generating automated replies. If you're using Postmark, SendGrid, or Mailgun for transactional email, they handle this automatically when you use their reply-tracking features.

Still one thing to note: In-Reply-To doesn't affect deliverability. Spam filters don't care if your threads are organized. This header is purely for user experience. A broken thread won't land you in spam, but it will annoy your recipients when they can't follow a conversation.

If you want to see In-Reply-To in action, grab the raw source of any reply in your inbox (most clients have a "View Source" or "Show Original" option) and look for the In-Reply-To: line. You'll also see a related header called References, which lists the entire chain of Message-IDs in a multi-reply thread.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Get personalized help with email threading

I read this on the Email Almanac about the In-Reply-To header: "The In-Reply-To header tells an email client 'this message is a reply to that specific email over there.' It references the Message-ID of the email you're replying to. Without it, your reply just looks like a brand new email, and the conversation thread falls apart." Help me understand how this applies to MY specific situation: 1. Why my email threads might be breaking (replies showing up as new messages instead of in the conversation) 2. What to check if I'm building transactional emails that people reply to (support tickets, order confirmations) 3. How to verify In-Reply-To is set correctly in my outgoing emails 4. Whether this affects deliverability or just user experience --- My details (the more you share, the better the advice): - Email platform/ESP: e.g. Postmark, SendGrid, Gmail, custom SMTP - What I'm building: [support system, order notifications, newsletter, conversational email] - Current challenge: [e.g. replies aren't threading, building reply-tracking, debugging broken conversations] - Technical level: beginner / intermediate / advanced

Edit the yellow boxes, then send to the AI of your choice.