Inside
The parts of Postkontor that do not need DNS: the reader for zone files, which turns what a DNS provider exports into records and writes the fixes back; the merge that puts the platform into a domain’s own SPF record without taking anything away; the ownership token; and the lifecycle a domain moves through.
Zone file
RFC 1035’s format: $ORIGIN and $TTL, @ and names relative to the origin, a blank name that repeats the one above, comments, strings in quotes and parentheses that run over lines. A line the reader cannot read is reported with its number, and the lines around it are kept.
| Line | Name | TTL | Type | Value |
|---|
Written back
SPF merge
A domain that already sends mail elsewhere has an SPF record, and a second one makes both fail. The merge puts the platform’s include into the record that is there: before all or redirect, keeping every sender and the record’s own all.
Mechanisms, separated by spaces.
| Term | Qualifier | Counts a lookup |
|---|
Ownership token
HMAC-SHA-256 over the account and the domain with the platform’s key, the first 160 bits written in base32. The same account and domain always give the same token; another account gives another.
Lifecycle
The states a domain moves through and what moves it. An event that does not apply in a state leaves the domain where it is.
| State | What moves it on |
|---|---|
| Waiting for proof | The ownership record is found: provisioning. 14 days without it: released. |
| Provisioning | The mail server has the domain and its keys: waiting for records. |
| Waiting for records | A check finds every required record right at both resolvers: active. |
| Active | 2 checks in a row find a required record wrong: degraded. |
| Degraded | One check finds them right again: active. |
| Suspended | The payment resumes: back to where it was, and an active domain is checked again. |
| Released | Nothing. Another account proving the domain releases it from any state. |