Email infrastructure wiki.
No fluff, no SEO theatre.

Reference standards and editorial discipline for the wiki

The wiki entries follow editorial standards that distinguish reference content from marketing content. The structural reasoning is that operators using the wiki for technical decisions need accuracy and operational substance over persuasive framing. Marketing content reads differently from reference content, and operators reading reference content for technical guidance benefit from the wiki resembling technical documentation rather than promotional material.

Editorial standards applied across all wiki entries: direct prose without marketing language, specific numbers and dates where applicable rather than vague approximations, honest acknowledgment of limitations and uncertainties, citation of operational evidence rather than appeals to authority, consistent terminology across entries to support cross-referencing, dated and updated entries rather than evergreen-positioning that obscures content age.

What the standards exclude: hype language that overstates capabilities, qualified language that hedges every claim, marketing-style headers and subheaders that fragment reading flow, repeated calls to action that interrupt technical content, vendor promotion disguised as objective reference. The exclusions matter because each pattern undermines the operational utility of reference content.

The standards apply uniformly across the 30 entries currently in the wiki. New entries added through 2026 will follow the same standards; existing entries are reviewed periodically and updated when standards drift over time or when new information warrants substantive revision. The review cadence is approximately quarterly with concentrated effort during periods when industry conditions warrant rapid documentation updates.

Wiki structure and content navigation

The wiki is organized for direct navigation rather than guided learning paths. The structural choice reflects that operators using technical reference content typically know what they are looking for; they need fast paths to specific entries rather than curriculum structures that assume linear reading.

Entry categories: authentication mechanics (SPF, DKIM, DMARC, BIMI, MTA-STS, TLS-RPT), receiver-side operations (Postmaster Tools, SNDS, FBL, blocklists), sender-side practices (warmup, reputation management, list quality, bounce processing), infrastructure topics (PowerMTA, MailWizz, dedicated vs shared IP, rDNS), business and operational considerations (DMCA, offshore jurisdictions, KYC hosting, payment infrastructure), specialized topics (Tor onion mirrors, EOTK, cryptocurrency payment integration).

Entry length varies based on topic complexity. Authentication topics average 4,500-5,500 words because the operational implications are substantial; practical implementation requires significant context. Single-concept topics average 3,500-4,000 words. Compound topics (interactions between multiple concepts) typically run 4,000-5,000 words because the interactions require explicit discussion alongside the individual concept coverage.

Cross-references appear at the end of each entry under the 'related' section. The references identify other entries that operators reading the current entry typically also reference. The cross-references support the natural navigation pattern operators use rather than imposing a curriculum structure that operators would need to work around.

Wiki entries that operators reference most frequently

Across the 30 wiki entries, usage patterns are uneven. A small number of entries account for substantial fractions of total references because they address topics that affect most sending operations.

The most-referenced entries cluster around authentication topics: DMARC, SPF, and DKIM consistently rank among the top five entries by reference volume. The concentration reflects the 2026 enforcement landscape where authentication failures produce immediate operational consequences; operators consult these entries when configuring new infrastructure or diagnosing authentication-related issues.

Receiver-side topics also generate substantial reference volume: Postmaster Tools, SNDS, and the blocklist entries rank in the second tier. Operators consult these entries when troubleshooting placement issues or investigating reputation events that monitoring infrastructure surfaces.

Specialized topics generate lower aggregate reference volume but higher per-operator depth. Operators referencing the EOTK or onion mirror entries typically reference them extensively while implementing the underlying capability; operators referencing the offshore jurisdictions entry typically reference it during strategic decision conversations rather than routine operations. The depth versus breadth pattern matches the underlying topic characteristics.

Cross-referencing patterns across wiki entries

Wiki entries cross-reference each other through the 'related' section at the end of each entry. The cross-references reflect operational dependencies between topics: operators reading about DMARC typically also need to understand SPF and DKIM; operators reading about Postmaster Tools typically also benefit from understanding DMARC and sender reputation.

The cross-reference network connects authentication topics, receiver-side topics, and operational practices into a navigable structure. Operators following cross-references typically work through 4-6 entries during deep diving on specific topics; the network supports the natural learning pattern of building from familiar topics to less familiar adjacent topics.

Cross-reference accuracy receives explicit review during entry updates. Operationally outdated cross-references can mislead readers; periodic review ensures the references reflect current operational reality rather than historical relationships that no longer apply.