An archive copy is not the inbox

Answer An archive copy is not the inbox. RFC 5064 defines the Archived-At header field. The field carries a URI where a stored copy of the message can be retrieved. The point is so a later reader of the headers can find the copy the archiver kept. The URI is not an open. It is not a click. It is not evidence that a person saw the creative in a mailbox.

The note that started this: RFC 5064, The Archived-At Message Header Field, RFC 5064.

June 21, 2026, is a Sunday, and it is Father's Day. People will mail offers into that morning and then point at a dashboard as if the day itself were a result. This note will not invent a holiday send. The useful distinction is older than the calendar. A copy you stored is a file you stored. A person who wanted the offer is a different event. If you are checking safe solo ads sellers, ask what they keep and what they count, and refuse to let one stand in for the other.

Archives exist for good reasons. A sender may need to know what they actually transmitted when a complaint arrives months later. A list host may keep a copy so support can answer a subscriber. Those are operational kindnesses. They become a problem only when the kindness is sold as performance. Performance is the reader. The header is a pointer.

What is the Archived-At header?

RFC 5064 defines a header that carries a URI where a stored copy of the message can be retrieved. The URI points at an archive. It does not mean a reader opened the message, and it does not mean a reader clicked.

A URI is an address for a resource. Someone who has access can fetch the copy, if the copy is still there, if the access rules allow it, and if the archiver told the truth in the header. That is a stack of ifs. A buyer looking at a screenshot of a header has not fetched the copy. A buyer who fetches the copy has seen what was stored. Neither step is a reader in a mailbox opening the mail on Sunday morning.

Access matters. An archive URL that anyone on the internet can open may publish a creative, and sometimes a recipient address, further than you meant. An archive URL that only the vendor can open is useless as proof unless they open it with you. Ask which kind they use before you agree to have your offer stored there. Storage without a conversation about access is how creatives leak.

• The archive is described as storage.
• Clicks are counted on a link you control.
• A complaint review uses the stored creative, not a reconstructed one.
• Access to the copy is stated before the send.

Is an archive copy the same as the message in the inbox?

No. The archive is a copy kept where the archiver put it. The inbox copy is whatever arrived, and whatever the mailbox later did with it. Those can diverge. Ask which one a dispute is about.

Divergence is ordinary. A relay can add a footer. A security tool can rewrite a link. A mailbox can clip a long message. The stored original and the delivered bytes are allowed to be different objects. When a reader says the mail looked like a scam, and the seller says the archive looks fine, you are comparing two objects. Ask to see the delivered headers from a mailbox you control, sent through the same path. The archive can explain what they meant to send. The delivered copy explains what a mailbox received.

Do not let the archive win the dispute by default because it is easier for the seller to open. Easier is not truer. The buyer's test message is the fair exhibit. Send one to yourself before the drop, and keep it.

Should a solo ad buyer treat an archive link as a result?

No. A result is a person who took the action you paid for. An archive link is a storage address. If the seller's proof is only a stored copy, you have proof they kept a copy, not proof anyone wanted it.

Want is the standard. A stored copy of an unwanted letter is a well-filed unwanted letter. Filing is cheap. Desire is not. When the report arrives, ask for accepted recipients, clicks on your link, and the action those clicks produced. The archive URI can sit in an appendix for the day someone needs to know which creative flew. The appendix is not the invoice.

RFC 5064 gave stored mail a header so the copy could be found on purpose. Find it when you need the creative. Count people when you need a result. An archive copy is a copy. The inbox is where a person might have been, and might is not a sale.