Wdrożenie własne
Add your domain
Provisioning, DKIM, and the records that have to be published.
Zaktualizowano:
Niniejsze tłumaczenie ma charakter informacyjny. W przypadku jakichkolwiek rozbieżności wiążąca jest wersja angielska.
A domain is added from the administration console and moves through an explicit sequence: created on the mail server, DKIM key generated, DNS published, DNS verified, active. The sequence is resumable — an instance restarted halfway through continues from the last saved step rather than starting over.
Add it
Adding the domain creates it on the mail server and generates its DKIM signing key. Until the records are published, the domain waits, and the console shows which step it is on.
Publish the records
The console lists the exact records for the domain, including the generated DKIM public key. They are published at whoever hosts the DNS zone, not here.
What each record is for
- MX directs incoming mail to the instance
- SPF states which servers may send for the domain
- DKIM signs outgoing mail so a receiver can verify it
- DMARC tells receivers what to do when a check fails, and where to report
- MTA-STS and TLS reporting require encrypted delivery and report on it
Reverse DNS
Set the reverse record for the sending address to the mail hostname, at the provider that owns the address. Mail from a host with no matching reverse record is rejected or filed as spam by several large receivers regardless of everything above.
When a domain stays pending
Propagation takes time; the instance re-checks on its own and activates the domain when the records answer. A domain that stays pending well past propagation is reported with the record it is still waiting for, so the wait can be told apart from a mistake.
For a local trial against a domain that does not resolve, DNS verification can be skipped. It must never be skipped in production: it is the check that the domain is really yours.