FluentSMTP does not create SPF or DKIM records. It connects WordPress to a mail service; the service supplies the authentication values, and whoever manages your domain’s authoritative DNS publishes them. To set this up safely, identify every service that sends mail for your domain, edit the active DNS zone, then configure FluentSMTP and test a delivered message.
How do I set up SPF and DKIM for FluentSMTP?
Work through these seven steps. The exact DNS values and SMTP settings depend on your email provider, so use its instructions rather than copying a generic record or assuming a UK web host controls your DNS.
- Identify every sender. Decide whether WordPress will send through a hosting mailbox, a transactional email service, or another SMTP/API provider. Include every legitimate service that sends messages using your domain, such as website notifications and other business email.
- Find the authoritative DNS zone. Check which nameservers the domain uses. The active zone may be managed by the registrar, web host, or a separate DNS provider. Make changes there, not simply in whichever control panel is easiest to find.
- Inspect the existing SPF record. Find the domain’s current TXT record beginning with
v=spf1. Keep one SPF policy for the domain and merge authorized senders according to each provider’s instructions. Do not add a second SPF policy or replace a working one without accounting for its existing senders. GOV.UK’s email security guidance says SPF should cover all systems that send mail for the domain; its specific requirements apply to government services. - Publish the sender’s DKIM record. In the sending provider’s dashboard, obtain the exact record type, selector, and value or target. A selector owner name often looks like
selector._domainkey, but use the supplied name and value exactly. The provider may require a TXT record or a CNAME. After publishing it, use the provider’s verification control to confirm it can see the record. GOV.UK’s guidance describes the selector pattern and notes that some providers use CNAME records. - Add DMARC carefully. DMARC is a TXT record at
_dmarc. If you have not confirmed that every legitimate mail stream passes aligned SPF or DKIM, a monitoring policy such asp=nonecan be a cautious starting point while you review reports. Once legitimate senders are accounted for, consider moving toward quarantine or reject. GOV.UK’s implementation advice is written for government email administration; do not copy its reporting address or treat its requirements as automatic rules for every private UK website. Its separate guidance for domains that do not send email gives a different protective policy. Do not apply that no-sender policy to a domain used by WordPress or another mail system. - Configure FluentSMTP. Use the provider’s native API connection if it is available and supported. Otherwise select Other SMTP and enter the actual server hostname, port, encryption mode, username, and password or app password provided by the mail host. FluentSMTP’s general host guidance gives 465 with SSL and 587 with TLS as typical settings, but your provider’s settings take precedence. Use a From address on a domain the provider permits.
- Send a real test and inspect authentication. Send to an external mailbox, then open the message’s original/source or authentication details. Look in
Authentication-Resultsforspf=pass,dkim=pass, anddmarc=pass. A FluentSMTP connection test confirms that WordPress can reach the sending endpoint; it does not prove that DNS authentication passed or that the message avoided spam.
Where do I add SPF and DKIM records?
Add them in the authoritative DNS zone for the domain. A UK-hosted WordPress site, its email service, its registrar, and its DNS provider can all be separate services. Your hosting control panel is the right place only if that host actually manages the domain’s active DNS.
The mail provider supplies the record values; the DNS administrator publishes them. For SPF, that usually means editing the existing policy rather than creating another. For DKIM, copy the provider’s record type, name, and value or target exactly, including the selector.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
DNS visibility is not instantaneous or guaranteed on a fixed schedule. FluentSMTP’s June 30, 2026 setup guide says changes can appear in minutes or take several hours. Check the sending provider’s verification control and confirm the record in the authoritative zone rather than relying on a promised wait time.
Does FluentSMTP set up SPF automatically?
No. FluentSMTP routes WordPress mail through a sending service; it does not publish SPF, DKIM, or DMARC records in DNS. The sending provider gives you its required SPF and DKIM details, and the DNS zone owner adds or updates the records.
DKIM also requires the sending provider to sign outgoing messages. A DKIM record visible in DNS is not, by itself, proof that messages are being signed; confirm both provider-side verification and the message’s authentication results.
How do I choose a sending service for a UK hosting account?
A working hosting mailbox may be suitable if it provides authenticated sending, usable SMTP settings, and the DKIM support and records you need. If the host disables PHP mail, blocks the required outbound connection, or cannot support signing and authentication, use a compatible transactional service/API or another authorized SMTP provider. FluentSMTP says native API connections are more reliable when available and recommends a dedicated service to help maximize deliverability; those are product recommendations, not comparative performance results.
Recommended Free Tools
Compare the available options against your own sending needs:
- Whether the provider supports a FluentSMTP native connection or API, or requires generic SMTP.
- Whether it signs messages with DKIM and provides a way to verify the DNS record.
- Whether you can authorize every legitimate sender without creating competing SPF policies.
- Sending limits that suit your expected volume, plus domain or account verification requirements.
- SMTP port, encryption settings, and any outbound restrictions imposed by the WordPress host.
- Access to delivery logs and support when authentication or sending fails.
The cited material does not establish comparative provider performance or pricing, so it does not support ranking services or promising inbox placement.
What happens if I configure more than one FluentSMTP connection?
FluentSMTP can route messages according to their From address. Messages that do not match a configured From address use the Default connection; if that sending operation fails, FluentSMTP can try the Fallback connection. Its multiple-connections documentation clarifies that fallback is for send failures such as an API error, authentication error, or timeout. It does not retry a message simply because the message landed in spam.
How do I troubleshoot FluentSMTP authentication and sending?
- Connection timeout: confirm the SMTP hostname and port, and ask the host whether outbound port 25 is blocked. FluentSMTP’s troubleshooting guidance says many hosts block outbound 25 and suggests using 587 or 465 when supported by the provider.
- Authentication failure: check the mailbox username and password, and confirm whether the provider requires an app password.
- SSL/TLS error: make the encryption mode match the selected port and the provider’s stated settings.
- Provider cannot verify DNS: confirm you edited the authoritative zone, copied the exact record name and value, and used TXT or CNAME as requested. Allow for DNS visibility delay, then run the provider’s verification again.
- Mail sends but reaches spam: inspect the message’s SPF, DKIM, and DMARC results and alignment; verify that the From domain is authorized; and review the sending provider’s logs. A fallback connection does not fix spam placement.
What should a successful test show?
Check the received message’s authentication details, not just FluentSMTP’s connection status. Ideally, its Authentication-Results shows SPF, DKIM, and DMARC passing. If one fails, use the failing result to narrow the cause: SPF points back to the authorized sender policy, DKIM to the provider’s signing and published selector record, and DMARC to the policy and alignment of authenticated mail. Passing authentication is a useful diagnostic result, not a guarantee that a message will land in the inbox.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
