Why your email goes to spam, and how to fix it
SPF, DKIM and DMARC explained without jargon, and the order to fix them in.
6 min read · last updated 2026-08-05
Most deliverability problems are not caused by your message content. They are caused by receiving servers being unable to verify that you are allowed to send from your domain. Three records fix that, and they should be set up in this order.
1. SPF: who is allowed to send
SPF is a DNS record listing the servers permitted to send mail for your domain. If you send from your hosting, from a bulk email platform and from an accounting system, all three need to be in it.
You may only have one SPF record. Two SPF records is worse than none, because receivers treat it as an error.
v=spf1 include:_spf.example-host.com include:_spf.example-sender.com ~all2. DKIM: proof the message was not altered
DKIM signs outgoing mail with a private key and publishes the public key in DNS. Receivers verify the signature, which proves the message genuinely came from your domain and was not modified in transit.
DKIM is enabled per sending service. Enabling it on your mail host does not sign mail sent by your newsletter platform.
3. DMARC: what to do when checks fail
DMARC tells receivers how to treat mail that fails SPF and DKIM, and where to send reports. Start in monitoring mode, read the reports, and only then tighten the policy.
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com; fo=1Do not start at p=reject
Setting a reject policy before you know every legitimate sender will silently destroy real mail — invoices, password resets, order confirmations. Run p=none for at least two weeks and read the reports first.
What else affects delivery
- Sending bulk mail from a normal mailbox. Use a bulk platform; it protects your domain reputation.
- A mismatch between the From address and the authenticated sender.
- Buying lists. Recipients marking mail as spam damages reputation faster than anything else.
- A compromised password causing outbound spam. Enable two-factor authentication.
Did this answer your question?
If not, our support team would rather hear about it than have you struggle.
Ask a question