Fastmail: what you should know
Fastmail from Australia specifies a fixed set of records for custom domains: two MX hosts under messagingengine.com, three CNAME records for DKIM and one SPF record. Custom domains require at least one admin of the account to be on a plan other than Basic.
The SPF record stands out: Fastmail ends it with ?all, the neutral result, rather than ~all or -all. It fits that Fastmail does not require DMARC and names p=none as a start. If you want to protect the domain against abuse, you tighten both yourself once DKIM is in place.
At least one admin of the Fastmail account needs a plan other than Basic; the domain is added in the settings under “Domains”.
The values for Fastmail at a glance
The records Fastmail expects for a custom domain; the guides above cover the details.
- MX: 10 in1-smtp.messagingengine.com and 20 in2-smtp.messagingengine.com
- SPF: v=spf1 include:spf.messagingengine.com ?all
- DKIM: Fastmail requires three CNAME records for DKIM: fm1, fm2 and fm3 under _domainkey. Each points to a host at Fastmail that contains your domain in its name, following the pattern fm1.your-domain.dkim.fmhosted.com.
- DMARC: Fastmail writes that a domain works without a DMARC policy and names v=DMARC1; p=none as the record. That is the minimum value: it meets the requirements large receivers place on senders but changes nothing about delivery.
Where to create the records
Fastmail specifies the values; they are created at the domain’s DNS host, the place the name servers point to. The guides by host show the way to the DNS editor of IONOS, STRATO, Hetzner, Cloudflare and other providers.