Sending Email with Previously Used Message-ID

If you send an email with a Message-ID header that perfectly matches an email you have already sent, it violates the core email standard (RFC 5322), which dictates that every Message-ID must be globally unique.

Because email systems rely heavily on this uniqueness, sending a duplicate Message-ID will cause a series of unpredictable and usually negative results at the receiving end.

Here is exactly what is likely to happen:

1. Silent Dropping (Deduplication)

This is the most common outcome. Most modern mail servers (such as Microsoft Exchange, Office 365, and Google Workspace) have built-in duplicate suppression.

  • When the receiving server sees an incoming email with a Message-ID it already has in its database, it assumes the email is an accidental duplicate caused by a network glitch or a delayed retry from a sending server.
  • The server will accept the email at the SMTP level (giving you a 250 OK success message), but the local delivery agent will silently discard it. The recipient will never see the second email, and you will not get a bounce message.

2. Bizarre Threading and Display Issues

Email clients (like Gmail, Outlook, and Apple Mail) use the Message-ID—along with In-Reply-To and References headers—to group emails into conversation threads.

  • If the server actually delivers the message, the recipient's email client will be thoroughly confused.
  • The client might assume the second email is just a cached copy of the first one and hide it entirely.
  • If the second email has different body content but the same Message-ID, the client might visually merge the two, attach the new email to a completely unrelated conversation thread, or cause weird display glitches for the recipient.

3. Triggering Spam Filters

Spam filters and security gateways heavily scrutinize Message-ID headers.

  • Reusing a Message-ID is a strong indicator of poorly written spam software, a malfunctioning script, or a compromised mail server.
  • Spam filters track previously seen identifiers. Seeing a duplicate will significantly raise the email's spam score, likely sending it straight to the Junk folder or causing the receiving server to quarantine it.

Summary

While the sending SMTP server will usually let the message leave your outbox, the receiving end will handle it poorly. The message will likely be silently deleted, routed to spam, or hidden by the recipient's email client.