{{define "content"}}
This password is shown once only and is not stored. Copy it now — if it is lost, regenerate a new one.
Publish this TXT record in the DNS for {{.Domain.Name}}. It is not a secret and can be viewed at any time.
Mail is signed with selector {{.Domain.DKIMSelector}}.
These two are not generated the way the DKIM record above is —
they are policy, and the domain may already publish an SPF record for other
senders. SelfPost is a send-only relay — most operators have no inbox on the
sending domain, so the suggested DMARC record omits rua= unless a
report address is configured below or in Settings.
Publish both as TXT records.
A domain may have only one SPF record. If it already has one,
do not add a second — add this server's mechanism to the existing record
instead, before its all term.
The report address is on this sending domain. SelfPost does not receive inbound mail — use a mailbox elsewhere or wait for in-panel report reception in a future release.
{{end}} {{if .NeedsReportAuth}}p=none changes nothing about delivery. Omit
rua= on a send-only domain, or point it at a mailbox that
receives inbound mail. Tighten to p=quarantine and then
p=reject once aggregate reports look clean.
What DNS publishes for {{.Domain.Name}} right now, checked against the key this server signs with. Results are cached for a few minutes — after publishing a record, use Re-check.
{{.DNS.DKIM.Detail}}
{{if .DNS.DKIM.Records}}{{range .DNS.DKIM.Records}}{{.}} {{end}}{{end}}{{.DNS.SPF.Detail}}
{{if .DNS.SPF.Records}}{{range .DNS.SPF.Records}}{{.}} {{end}}{{end}}The SPF check is deliberately shallow: it looks for a
mechanism that literally covers this server's address and does not follow
include: or redirect=, so a record that authorises
the server through an include is reported as “cannot tell”, not as a failure.
{{.DNS.DMARC.Detail}}
{{if .DNS.DMARC.Records}}{{range .DNS.DMARC.Records}}{{.}} {{end}}{{end}} {{if .DNS.DMARCReportAuth.Status}}{{.DNS.DMARCReportAuth.Detail}}
{{if .DNS.DMARCReportAuth.Records}}{{range .DNS.DMARCReportAuth.Records}}{{.}} {{end}}{{end}} {{end}}Point the mail client or script at these settings and authenticate with an application login and password from the Applications section below. They are the same for every domain on this server.
Authentication is required on every port. The username is the application's login (see the table below) and the password is the one shown once when that application was created or its password regenerated — if it was lost, generate a new one.
A strong password is generated and shown once. The login must be unique across all domains and may contain letters, digits, '.', '-' and '_'.
Each application is a SASL login/password an app or script uses to send mail as this domain. A login may send from any address of the domain (wildcard) or only from a fixed list of addresses.
{{if .Apps}}{{.Login}}
{{if eq .AddressMode $.Wildcard}}Any address of the domain — *@{{$.Domain.Name}} {{else}}Fixed list — {{range $i, $a := .Addresses}}{{if $i}}, {{end}}{{$a}}{{end}}{{end}}
No applications yet. Add one above to get started.
{{end}}Optional level-2 limit (spec 7.4): cap how many messages this domain may send from its expected client IP(s) within a time window, summed across all its applications. It counts messages — one message to many recipients counts once. Leave the IP list empty to disable it and rely only on the global level-1 limit. Applications that send from changing IPs should be left unbound here.
Status: {{if .DomainHasRL}}active{{else}}inactive (level-1 only){{end}}.
{{if .DomainHasRL}} {{end}}Download this domain to move it to another SelfPost instance: its DKIM key, selector and every application with its working password. On import the DNS record stays the same, so no DNS change is needed.
The export file is a secret — it contains the
private DKIM key and application passwords. Transfer it securely and delete it
after the import, or encrypt it below and move a .spde file
(SelfPost domain export) instead; the import form asks for the password.
{{.ExportErr}}
{{end}}Deleting this domain also deletes its DKIM key and every application bound to it.
Delete domainOn this page
{{if .NewCred}}New application password{{end}} DKIM DNS record SPF and DMARC records DNS status Sending server settings Add an application Applications Sending rate limit Export domain Danger zone