Privacy-focused email hosting service with custom domain support. This guide covers the complete email authentication stack for Fastmail: SPF, DKIM, and DMARC. Each section gives you the exact DNS records, step-by-step instructions, common pitfalls, and how to verify your setup.
Authorize Fastmail to send email on behalf of your custom domain by adding the correct SPF include.
TXT
@
v=spf1 include:spf.messagingengine.com ~all
Fastmail's parent company is Messaging Engine. The SPF include uses their infrastructure domain.
Go to fastmail.com and sign in to your account.
Go to Settings > Domains. Select your custom domain.
Fastmail displays all required DNS records including SPF, DKIM, and MX.
Add a TXT record with the SPF include for Fastmail.
v=spf1 include:spf.messagingengine.com ~allFastmail will check your DNS records and show verification status.
v=spf1 ~allv=spf1 include:spf.messagingengine.com ~allAdd include:spf.messagingengine.com to your SPF record. This is Fastmail's sending infrastructure domain.
Messaging Engine Pty Ltd is Fastmail's parent company. Their email infrastructure runs under the messagingengine.com domain.
Yes. Fastmail requires MX records pointing to in1-smtp.messagingengine.com and in2-smtp.messagingengine.com for receiving email.
Enable DKIM for Fastmail by publishing three CNAME records for the fm1, fm2, and fm3 selectors.
CNAME
fm1._domainkey
fm1.yourdomain.com.dkim.fmhosted.com
Fastmail uses three DKIM selectors: fm1, fm2, and fm3. All three CNAME records must be added.
Go to fastmail.com and sign in.
Go to Settings > Domains. Select your custom domain.
Fastmail displays three CNAME records for DKIM with selectors fm1, fm2, and fm3.
Create the three CNAME records in your DNS provider.
fm1._domainkey.yourdomain.com CNAME fm1.yourdomain.com.dkim.fmhosted.com
fm2._domainkey.yourdomain.com CNAME fm2.yourdomain.com.dkim.fmhosted.com
fm3._domainkey.yourdomain.com CNAME fm3.yourdomain.com.dkim.fmhosted.comFastmail will verify the DKIM records and activate signing.
Fastmail uses fm1, fm2, and fm3 as DKIM selectors. All three are published as CNAME records pointing to fmhosted.com.
Three selectors allow Fastmail to rotate DKIM keys smoothly. One selector is active while others are prepared for rotation.
Yes. If you use Fastmail's nameservers for your domain, DKIM (and all other records) are configured automatically.
Publish a DMARC record to protect your custom domain when using Fastmail for email.
TXT
_dmarc
v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1
Fastmail provides SPF and DKIM alignment by default when properly configured.
Set up SPF (include:spf.messagingengine.com) and DKIM (fm1/fm2/fm3 CNAMEs) for Fastmail.
Send a test email from Fastmail and verify SPF and DKIM pass in the headers.
Add a TXT record at _dmarc.yourdomain.com.
v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1Review DMARC aggregate reports. Fastmail typically has clean alignment.
Fastmail provides good alignment. After confirming, move to p=quarantine and then p=reject.
Yes. Fastmail provides both SPF and DKIM alignment when properly configured with a custom domain.
Yes. Fastmail has excellent authentication support. If Fastmail is your only sender, you can safely use p=reject.
If you use Fastmail's nameservers, they can set up the DMARC record for you. Otherwise, add it manually to your DNS.
Once your SPF, DKIM, and DMARC records are in place, run a full domain scan to confirm everything is configured correctly. DNS changes typically propagate within minutes but can take up to 48 hours.