DIAGNOSTIC PLAYBOOK
Use Message-ID to trace an email across systems
Message-ID can help correlate a message across logs, but it is not a cryptographic proof of origin or a guarantee of uniqueness. Pair it with timestamps and provider-specific identifiers.
HealthCheck Email editorial team · · Examples are illustrative
How to investigate
- Copy the full Message-ID from the original message without altering its brackets or domain portion.
- Search the sender and receiver logs within the relevant time window.
- Cross-check recipients, queue IDs and routing information to distinguish copies or reused identifiers.
What this looks like
ILLUSTRATIVE EXAMPLE
A helpdesk and sending platform both log the same Message-ID. Their own event IDs then connect the message to a specific submission and delivery attempt.
A mistake to avoid
Do not assume the domain in Message-ID is the authenticated sender. Applications can construct that field independently of their actual sending identity.
Keep the result in context
Inspect the original raw message rather than a forwarded screenshot. Headers can contain private addresses, message identifiers and routing information, so redact a separate copy before sharing. Give the most weight to results added by your own trusted receiving infrastructure.
Take the next step
Use the related check to gather evidence, then compare it with the affected message or service. Keep the result and time with your notes so a later change can be distinguished from the original problem.
Sources and further reading
The protocol references below explain the underlying behavior. Your sending or DNS provider supplies the account-specific settings for its service.