Opens in a new tab
🚀 Your daily business tech & AI briefing — Subscribe free →

FluentSMTP SPF & DKIM: the honest 7-step setup

Zain A
Share this article

Introduction

Why authenticated email still lands in spam

If your FluentSMTP emails keep landing in spam, your DNS isn’t ready — without SPF and DKIM, most providers throttle or bin your mail. Here’s the no-nonsense, 7-step setup that actually works, including the exact DNS records to add and how to verify them from a real message header.

What FluentSMTP does and does not sign

FluentSMTP routes wp_mail through your provider. The DKIM keys come from that provider, and you publish them in DNS.

FluentSMTP SPF & DKIM: the honest 7-step setup

Choose the Email Provider Behind FluentSMTP

Amazon SES, Brevo, SendGrid or Google Workspace

FluentSMTP connects to many services, including Amazon SES, Brevo, SendGrid, Mailgun, Postmark, SparkPost, SMTP2Go, Elastic Email, Netcore, Microsoft Office and Gmail or Google Workspace.

Pick one that fits how your site sends mail:

  • Transactional services such as Amazon SES, Postmark or SendGrid suit order confirmations and password resets.
  • Brevo suits sites that also send newsletters.
  • Google Workspace suits small sites that already send from a Gmail-based business address.

Why the provider decides your records

Your SMTP service names the servers your SPF record must include. Every provider supplies different values.

Choose first, then build your DNS records around that choice.

Connect Your Domain in the Provider Dashboard

Add the sending domain

Log in to your chosen provider and find the section for domains or senders. Enter the domain you send WordPress email from, such as yourbusiness.com.

The provider then starts a verification process. It stays pending until your DNS records are in place.

Copy the DNS values it gives you

The dashboard displays the records you need to publish. Copy each one exactly as shown.

  • DKIM records, usually TXT or CNAME entries that carry your DKIM signature keys
  • The SPF details, meaning the servers your SPF record must include
  • Any extra verification record the provider requires

Keep these values open in a separate tab. You will paste them into your DNS settings in the next steps.

Publish a Single SPF Record in DNS

Including your provider’s servers

An SPF record is a TXT record published in your DNS settings. It lists the servers allowed to send email as your domain.

Add your provider’s include value from the dashboard to that record. Use exactly the value your provider supplied.

  1. Open the DNS settings for your domain.
  2. Create a TXT record on the root domain.
  3. Paste the SPF value with your provider’s include.
  4. Save the record.

The one-record and 10-lookup limits

A domain should have only one SPF record. If you already send through another service, merge its include into the existing record instead of adding a second one.

SPF is also limited to 10 DNS lookups. Each include counts toward that limit, so remove services you no longer use.

FluentSMTP SPF & DKIM: the honest 7-step setup

FAQ

Does FluentSMTP sign emails with DKIM itself?

No. Your connected provider issues the DKIM keys, and you publish them in DNS.

How many SPF records can a domain have?

One. Merge additional services into that record.

Where do you add a DMARC record?

Publish it as a TXT record in your DNS settings.

Do SPF and DKIM apply to subdomains automatically?

No. DMARC inherits from the root domain to subdomains, but SPF and DKIM do not.

Conclusion

Email authentication starts with your provider. Choose it, add your domain, publish one SPF record and add the DKIM records it supplies. Then add a DMARC record.

References

Share this article

Stay in the Loop

Weekly tech insights, AI news and tools — straight to your inbox.

Newsletter Form (#4)

Contents