Email headers and hashes
A printed email shows who, when and what. The header lines behind it show how the message travelled, and the fingerprint shows the file has not changed since you exported it. That is usually what the other side's lawyer asks about first.
What the header lines show
Received:- Every mail server that handled the message adds one line at the top: which server it came from, which one took it, and the time,
with that server's clock and UTC offset. Read from the bottom up, they trace the route from the sender's provider to yours. The
sender's own
Dateheader comes from their device and can be set to anything; the times in theReceivedlines come from the servers, so they are the harder ones to fake. DKIM-Signature:- A digital signature the sending domain puts over the body and chosen headers (From, To, Subject, Date…). If someone later edits the text, the signature no longer matches. Checking it needs the domain's public key from DNS; Court Copy does not go online, so it prints the signature for an expert to check rather than checking it itself.
Authentication-Results:- What the receiving server (Gmail, Outlook…) concluded on arrival: whether SPF, DKIM and DMARC passed. It is the receiving provider's own record, made when the message arrived.
Message-ID,In-Reply-To,References- A unique ID for each message, and the IDs of the messages it answers. Court Copy builds threads from them, and they tie a reply to the exact message it replied to.
Return-Path,Delivered-To,X-Original-To- Where bounces go, and which mailbox the message was finally delivered to. Court Copy uses
Delivered-Toto name the mailbox owner on the cover.
Court Copy prints all of these, exactly as stored, in an appendix at the end of the PDF, numbered like the messages. Gmail shows the same lines under Show original; Outlook under View → Message details; Apple Mail under View → Message → All Headers.
What a SHA-256 fingerprint proves
A SHA-256 is a 64-character number computed from every byte of a file. Change one character and the number is completely different.
The cover of a Court Copy PDF lists the SHA-256 of each file you chose (the .eml files, the .mbox, the
Takeout .zip), and each message carries the SHA-256 of its own bytes. So:
- It does show that the file someone checks later is exactly the file the PDF was made from. Anyone can compute it
again:
certutil -hashfile message.eml SHA256on Windows,shasum -a 256 message.emlon a Mac,sha256sum message.emlon Linux. - It does not show that the email itself is genuine. That is what the
Receivedlines, the DKIM signature and the provider's own records are for, and what a forensic examiner looks at. - For a message inside an
.mbox, the per-message SHA-256 covers its bytes in that file, from the line after theFromseparator to the end of the message. For an.eml, it is the whole file.
Keep the originals
- Keep the exported files exactly as downloaded, next to the PDF. Opening an .eml in a mail program and saving it again can change its bytes.
- Note when and how you exported them (Google Takeout on what date, or which message you saved from which program).
- If the other side may ask for the messages in their original form, the
.eml/.mboxfiles are that form; the PDF is the readable copy that points back to them.
How to export: Gmail · Outlook, Apple Mail, Thunderbird. Then make the PDF.
This page explains what the files contain; it is not legal advice. Whether and how email is accepted is for the court, the lawyers and the other side to say.
Open Court Copy Full exports free right now, nothing uploaded.