“Our contact form stopped working.” In my experience, the form usually works fine. The submission is processed perfectly, and WordPress dutifully sends an email. That email just never reaches anyone. It’s rejected by the receiving server, lands in spam or silently disappears.
Email problems are among the most common issues on WordPress sites, and among the most damaging. Missed enquiries cost business. Order confirmations that don’t arrive make customers think their purchase failed. Password reset emails that vanish lock people out.
The good news is that the fix is well understood. It comes down to two things: sending email through a proper mail service instead of the web server, and authenticating your domain so receiving servers trust your messages.
Why WordPress email fails
By default, WordPress sends email using PHP’s mail function, which hands the message to the web server’s local mail system. That approach has several problems:
- The server isn’t a trusted sender. Web servers, especially on shared hosting, often have poor email reputations. Other sites on the same server may have sent spam.
- No authentication. The message claims to come from your domain, but nothing proves the web server is allowed to send for it.
- Mismatched sender details. Many forms send emails “from” the visitor’s address, which looks like spoofing to receiving servers.
- Some hosts disable mail entirely. Cloud providers often block outgoing email on standard ports by default.
Major email providers have also become much stricter. Since early 2024, Google and Yahoo require bulk senders to authenticate their email with SPF, DKIM and DMARC, and even smaller senders see better results with proper authentication. Unauthenticated email from a web server is increasingly likely to be rejected.
Step 1: Send through SMTP with a transactional email service
The first fix is to stop relying on the web server for mail. Instead, send WordPress email through an authenticated SMTP connection to a proper email service.
You have two main options:
- A transactional email service, designed for application emails such as order confirmations, password resets and form notifications. These services offer good deliverability, sending logs and APIs.
- Your existing email provider’s SMTP, such as a business email account. This can work for low volumes, but providers often limit how many emails you can send and may not be designed for application email.
For most business sites and stores, I recommend a transactional email service. They provide detailed logs showing whether each email was delivered, bounced or marked as spam, which makes troubleshooting much easier.
Connecting WordPress
An SMTP plugin replaces WordPress’s default mail sending with an authenticated connection. Several reputable plugins support popular email services through their APIs or standard SMTP. Configure:
- The service and API key, or SMTP host, port, username and password.
- A “From” email address on your own domain, such as [email protected] or [email protected].
- A “From” name customers will recognise.
Store credentials securely. Some plugins let you define them as constants in wp-config.php instead of the database, which keeps them out of database backups and exports:
The exact constant names depend on the plugin, so check its documentation.
Fix the “From” address on forms
Contact forms often use the visitor’s email address as the sender. That breaks authentication, because your service isn’t allowed to send email from gmail.com or a customer’s company domain. Instead:
- Send from your own domain address.
- Put the visitor’s email in the Reply-To header, so replying still goes to them.
Most form plugins have separate settings for “From” and “Reply-To”. Set them correctly on every form.
Step 2: Authenticate your domain
Authentication proves to receiving servers that your email really comes from you. Three DNS-based standards work together.
SPF
SPF, Sender Policy Framework, is a DNS TXT record listing which servers are allowed to send email for your domain. When a receiving server gets an email claiming to be from your domain, it checks whether the sending server is on the list.
An SPF record looks like this:
The include entries authorise your email providers. Your transactional email service and business email provider tell you exactly what to include.
Important rules:
- Only one SPF record per domain. Multiple SPF records cause failures. If you use several services, combine them into one record.
- Watch the lookup limit. SPF allows a maximum of ten DNS lookups. Each include can trigger several. Too many services can push you over the limit and break SPF.
- ~all versus -all. A soft fail (~all) is a common, safe choice while setting up. A hard fail (-all) is stricter once you’re confident everything is listed.
DKIM
DKIM, DomainKeys Identified Mail, adds a cryptographic signature to each email. The receiving server checks the signature against a public key published in your DNS. If the signature matches, it knows the email wasn’t altered and was sent by someone authorised to use your domain’s key.
Your email service gives you DKIM records to add, usually as TXT or CNAME records with names like selector._domainkey.example.com. Add exactly what they provide, then verify the domain in the service’s dashboard.
Each sending service needs its own DKIM setup. Your business email provider and transactional email service will each have their own keys.
DMARC
DMARC ties SPF and DKIM together and tells receiving servers what to do with email that fails authentication. It also checks alignment: the domain in the visible “From” address must match the domain authenticated by SPF or DKIM.
A starting DMARC record, added as a TXT record at _dmarc.example.com:
p=none means “monitor only”: receiving servers report failures but don’t reject emails. The rua address receives aggregate reports showing who is sending email for your domain and whether it passes.
Once reports confirm all your legitimate email passes, you can tighten the policy to p=quarantine, which sends failing emails to spam, and eventually p=reject, which blocks them. A strict DMARC policy also makes it much harder for criminals to send phishing emails pretending to be your business.
DMARC reports are XML files that are hard to read directly. Free and paid DMARC reporting tools turn them into readable dashboards.
Step 3: Test everything
After setting up SMTP and DNS records:
- Send a test email from your SMTP plugin’s test feature.
- Check the email headers in the received message. Look for spf=pass, dkim=pass and dmarc=pass in the authentication results. In Gmail, “Show original” displays these clearly.
- Use an email testing tool that gives you an address to send to and then scores your message, highlighting authentication problems and spam triggers.
- Test every email type: contact forms, WooCommerce order emails, password resets and user registration.
- Check your service’s logs to confirm emails are delivered, not bounced.
Step 4: Keep an eye on it
Email deliverability isn’t set and forget.
- Enable email logging in your SMTP plugin, or rely on your service’s logs, so you can confirm whether a specific email was sent.
- Monitor DMARC reports for new, unauthorised senders.
- Update SPF and DKIM when you add or change email services, such as a new newsletter platform or helpdesk.
- Watch bounce rates. Persistent bounces suggest bad addresses or a deliverability problem.
Content and reputation matter too
Authentication gets you in the door, but content and behaviour affect whether you stay out of spam:
- Use a consistent sending address and name.
- Avoid spammy subject lines and excessive capital letters.
- Include a plain text version along with HTML.
- Keep marketing email separate from transactional email, ideally using different services or subdomains, so newsletter complaints don’t harm order confirmations.
- Only email people who expect to hear from you.
Frequently asked questions
Why do my WordPress emails go to spam?
Most often because they’re sent from the web server without proper authentication, or with a “From” address that doesn’t match the sending service. Use SMTP with a reputable service and set up SPF, DKIM and DMARC.
Do I need a paid email service?
Many transactional email services have free tiers suitable for small sites. Stores and busy sites usually need a paid plan, which is inexpensive compared with the cost of lost orders and enquiries.
Can I use Gmail or Outlook SMTP?
You can for low volumes, but these accounts have sending limits and aren’t designed for application email. A transactional email service is more reliable for forms and store emails.
Will changing DNS records affect my existing email?
Adding SPF, DKIM and DMARC records doesn’t affect receiving email. But be careful when editing SPF. Removing an existing provider from the record can cause that provider’s emails to fail. Combine services into one record rather than replacing it.
Final thoughts
WordPress email problems are rarely about WordPress itself. They’re about sending mail from a server nobody trusts, without proof of identity. Route your site’s email through an authenticated SMTP service, send from your own domain, set up SPF, DKIM and DMARC, and test every type of email your site sends. Once that’s done, your forms, orders and password resets will arrive where they should.




