Message-ID

Message-ID is an email header that holds a globally unique identifier for a single message, written as a string in angle brackets with an at sign, such as a random value followed by the sender's domain. Mail clients use it to thread replies and detect duplicates.

Deliverability & Email InfrastructureUpdated September 30, 2026

In short

Message-ID is the unique fingerprint of an email, used for threading and tracing.

Key points

  1. RFC 5322 says every message should have a Message-ID, and that it must be globally unique to that one message [1].
  2. Replies copy the original Message-ID into In-Reply-To and References, which is how clients build an Email Thread [1].
  3. Gmail's sender guidelines ask that every message include a valid Message-ID [2].
  4. Gmail may rate-limit a sender that repeats the same Message-ID too often, returning a 421 4.7.28 quota error [3].
  5. Message-IDs are the standard key for matching bounces, replies and Feedback Loop (FBL) reports back to the message that caused them [1][4].

Format and uniqueness

RFC 5322 section 3.6.4 defines the Message-ID field as an identifier in angle brackets with a left part and a right part separated by an at sign [1]. The right side is usually the sending host or domain, and the left side is a random or time-based value that makes the whole string unique. The RFC requires the generating host to guarantee uniqueness, and in practice systems use long random strings or UUIDs combined with a domain they control [1]. The ID is created once, when the message is first composed or submitted, and should not change as the message passes through relays. Some mail servers add a Message-ID if the client left it out, but relying on that can produce IDs that reveal internal host names.

How Message-ID drives threading

When someone replies, their mail client puts the original Message-ID in the In-Reply-To header and appends it to the References header, which holds the chain of earlier IDs [1]. Clients use those fields to group messages into conversations, and Wikipedia's overview describes how the identifier supports threading and duplicate detection [4]. For Follow-Up Email steps in an Email Sequence, setting In-Reply-To and References to the earlier message keeps the follow-up in the same conversation in the recipient's inbox, which reads as a natural reply rather than a new cold message. PineLead sends from your connected mailbox and replies land back in the thread, so each conversation stays together in your own inbox.

Deliverability and troubleshooting

Missing or malformed Message-IDs are a formatting red flag. Gmail's sender guidelines ask that every message carry a valid Message-ID and follow RFC 5322 [2], and its SMTP error reference includes a rate-limit response for senders who exceed a quota for messages with the same Message-ID [3]. A system that reuses one ID for many sends, often a bug in custom sending code, can therefore be throttled. When tracing a problem, the Message-ID is the most reliable way to find a specific message in server logs, Email Headers of a delivered copy or bounce reports, since subject lines and timestamps are rarely unique. It also helps Reply Detection match an incoming answer to the right contact.

Sources
  1. RFC 5322: Internet Message Format — RFC Editor
  2. Email sender guidelines — Gmail Help
  3. Gmail SMTP errors and codes — Google Workspace Help
  4. Message-ID — Wikipedia
External sources open in a new tab.

Related terms

Mentioned in

Outreach without the busywork.

PineLead finds new B2B prospects every day, qualifies them against your criteria and writes the first email in your voice. You approve — PineLead sends.

Start free with 100 credits →