kith← writing
2026-06-08

The Research Behind Trust-Graph Email: TrustMail, Ostra, MeritRank

Short answer: Scoring email by relationship is not a new idea. It stands on twenty years of peer-reviewed work on trust networks and Sybil resistance. TrustMail and EMIRT pioneered relationship-based email triage, Ostra used trust links to throttle unwanted communication, and the EigenTrust and MeritRank line formalized how to keep such scores resistant to fake accounts. Here is the lineage, in plain terms.

TrustMail and EMIRT: trust-based email triage

Golbeck and colleagues proposed TrustMail, an email client that prioritizes messages using a trust network: a graph of who trusts whom, with messages from well-connected senders surfaced and unknown senders inferred through transitive trust. Later work, EMIRT, extended this by building the trust network implicitly from mail logs, the frequency of exchanges and replies, rather than asking users to enter scores by hand. It also added inter-recipient trust: who else is on a thread is itself a signal.

The takeaway that still holds: you can infer a usable relationship graph from email metadata alone, no manual input required.

Ostra: pay for cold contact with your trust links

Ostra (Mislove et al., NSDI) took a different angle. It used existing trust relationships to impose a cost on unwanted communication. A cold message spends credit along the trust path to the recipient, and if the recipient marks it unwanted, that credit is not refunded, straining the sender's links. It throttles spam without requiring strong global identities. This is the blueprint for a cold-sender challenge: a stranger reaches you by posting a bond through a trust path, refunded if you engage.

EigenTrust and the Sybil problem

The hard question for any reputation system is Sybil resistance: can someone spin up fake identities to inflate a score? EigenTrust brought PageRank-style trust aggregation to peer-to-peer networks. Cheng and Friedman then proved a sharp limit: a symmetric, global reputation function cannot be made fully Sybil-proof. This is why a single public score per sender is structurally gameable, and why a personalized score, seeded on you, is the more defensible design. See personalized vs public reputation.

MeritRank: bounding what attackers gain

More recent work, MeritRank (Nasrulin et al., TU Delft), accepts that you cannot fully prevent Sybil attacks and instead bounds the benefit. It applies decay mechanisms so that trust reaching you through long chains or through single bottleneck nodes is discounted. Notably, its experiments found that time-based (epoch) decay does not improve Sybil tolerance, while transitivity decay and connectivity decay do. Recency is a relevance signal, not a security one.

How it comes together

A modern trust-graph email engine combines these threads:

  • An implicit relationship graph from metadata (TrustMail, EMIRT).
  • Personalized PageRank seeded on the user, not a global score (EigenTrust, Cheng-Friedman).
  • Decay to bound Sybil amplification (MeritRank).
  • An optional bond mechanism for cold contact (Ostra).

The result is a sender score that is personal, resistant to fake-account rings, and computed from data already in your inbox. See PageRank for email for the mechanics.

FAQ

Is this an academic toy or a real product? The research is academic; the implementation is practical. Kith is an open-source engine that applies this lineage to Gmail.

Where can I read the papers? Search for TrustMail (Golbeck), EMIRT, Ostra (NSDI), EigenTrust, Cheng and Friedman "Sybilproof reputation mechanisms", and MeritRank.

Why does open source matter here? A trust system should be inspectable, not a black box. Read how to sort your Gmail by who you actually know.

SEE IT RUN

Sort your Gmail by who you actually know.

Connect Gmail →