Why Postmetry
The email audit seen from the inbox
Postmetry observes your emails the way a real recipient receives them. No access to your sending platform, no script, no simulation.
01 — Measured from the inbox
What your recipients receive. Not what your tools claim to send.
Most email tools describe their own configuration: campaign sent, authentication enabled, tracking configured, unsubscribe present.
Postmetry starts from the other end.
We receive your emails like any subscriber and analyze the message that actually arrived in the inbox: its headers, its HTML, its links, its trackers, its unsubscribe mechanisms, and the technical elements it contains.
That's what makes it possible to observe the final result, after it has gone through your sending platform and your infrastructure.
Incoming email
Private sales — final hours
- Headers Received · DKIM · SPF
- Authentication dmarc=pass
- Unsubscribe List-Unsubscribe
- Open trackers 1 detected
- Links 14 · 14 tracked
Example — an email read, item by item.
Nothing to connect
No plugin, no library to install, no admin access to your sending platform.
One of our addresses signs up to your communications. The emails received become the audit's material.
Your tools can change. The measurement stays the same.
Brevo, HubSpot, Salesforce Marketing Cloud, Mailchimp, Klaviyo, or in-house infrastructure: the analysis covers what arrives in the inbox, regardless of the tool that produced it.
02 — Proof for every finding
A score isn't enough. You need to be able to explain why.
An audit that answers “compliant”, “to check”, or “72/100” asks you to trust the tool. Postmetry keeps what makes it possible to establish each finding.
<img src="https://x791s.mjt.lu/o/dfe1…" width="1" height="1" alt="">The fragment is attached to the finding, with the date of the message that carries it.
A DKIM signature links back to the headers concerned. An unsubscribe mechanism links back to what was observed in the message. A detected tracker links back to the fragment that establishes it.
So you can see what was observed, and what the conclusion rests on.
The evidence stays attached to the finding
The relevant fragment of the message is kept with the analysis. A finding can be reread months later without depending on the state of the site or the sending platform at the time it's reread.
Rules evolve without rewriting the past
The raw message is kept. When an analyzer changes, the measurement is replayed on the same message.
So we distinguish what changed in your emails from what changed in how we analyze them.
03 — No resource loaded
Observe an email without triggering what it contains.
Opening an email normally already alters what we're trying to measure.
- A remote image signals an open.
- A tracker registers a request.
- A link passes through a tracking redirector.
Postmetry analyzes the message received without loading its remote resources.
No external image is fetched to perform the analysis. No link is visited to determine what the message contains.
Email received
- HTML analyzed
- Headers analyzed
- URLs analyzed
- Tracker ✕ remote server — not reached
- Image ✕ CDN — not reached
- Link ✕ redirector — not reached
No outbound request is made to the resources contained in the message.
The message stays a piece of evidence for observation
The analysis works on the content received, rather than turning the audit into one more interaction with the sender.
That's decisive when the very point is to establish the presence of tracking mechanisms.
No signal that we would have produced
Observing a tracker doesn't require loading it.
Its presence is read in the message, without producing the open it is precisely there to measure.
04 — Deterministic measurements
The same data. The same rules. The same result.
No language model decides whether an email carries a tracker, valid authentication, or an unsubscribe mechanism.
These findings are produced by deterministic, versioned analyzers, whose list and versions are published.
A given rule, applied to the same message, produces the same result.
Measured
Remote tracker present in the HTML
pixel analyzer v4 · pixel.detected
Interpretation
What this tracker is used to measure depends on the email's purpose, and this reading is flagged as such.
An interpretation feeds no ranking, no alert, no score.
Automation where it can be checked
Technical elements are extracted from the message itself: headers, HTML, URLs, and normalized structures.
Rules are tested, fixed, and replayed.
When a reading comes into play, it's visible
Not everything reduces to a regular expression.
When a piece of information rests on a reading rather than a measurement, it is distinguished from the measured finding, in the report as in the data.
05 — A European, immutable archive
Every email becomes a piece of audit evidence.
A campaign disappears from your tool. A setting changes. A template is modified.
The email actually received, on the other hand, is a dated state of your communication.
Postmetry keeps this raw message, so the analysis can be checked or replayed later.
14 Oct 2025
Message received
- Analysis replayed Nov 2025
- Analysis replayed Mar 2026
- Current analysis Sep 2026
Example — three replays on the same piece of evidence.
Written once
The original message is archived without ever being rewritten by successive analyses.
Results can change; the evidence they rest on does not move.
Hosted in the European Union
Archives are stored in the European Union, read-only.
In summary
A different method for auditing email
We receive the real email, we don't trigger it, we measure it with reproducible rules, we show the evidence, we keep the original.
| Criterion | Postmetry |
|---|---|
| Observation point | Email actually received |
| Connection to your sending platform | None |
| Remote resources during analysis | Not loaded |
| Technical findings | Deterministic and versioned |
| Justification | Proof attached to the finding |
| History | Original message retained |
| Archive hosting | European Union |
Your emails already contain the answers.
Postmetry receives them, analyzes them, and keeps what makes it possible to demonstrate each finding.
Frequently asked questions
What we're asked most often
Does Postmetry need access to my Brevo, HubSpot, or Mailchimp account? +
No. Postmetry observes emails from a dedicated inbox. No administrator access to your sending platform is needed.
Do I need to install a script or modify my site? +
Not to analyse the emails received. Postmetry works from the inbox and needs no script on your site to establish its findings on messages.
Does Postmetry open the open trackers? +
No. Analysing the message loads neither the images nor the remote trackers it contains: that's precisely what makes it possible to record their presence without producing the open they're meant to measure.
Does Postmetry click the links in my emails? +
Not to establish the findings. The analyzer counts the links, records their tracking domain, and spots an untracked path; it doesn't visit them.
Does Postmetry use a language model to analyse my emails? +
Technical findings rely on deterministic, versioned analyzers. When a piece of information comes from a reading rather than a measurement, it's kept distinct from the measured finding and feeds neither a ranking nor an alert.
What happens if the analysis rules change? +
Since the original message is kept, a new version of an analyzer can be applied to the same email. The analysis evolves without the evidence it relies on ever being modified.