Do your contact form messages never arrive? Do customers say that they did not get their order email, or that the password reset link never came?
Email problems are some of the most common WordPress problems, and they cost you real business. A lead that never reaches you is a lost lead. A customer who does not get a receipt may ask for a refund. And the worst part is that WordPress often says the message was sent, while the email never reaches the inbox.
The good news is that you almost never need to change your hosting. In most cases, the fix is to send your email through a proper email service, and to set up the records that prove your messages are real.
In this guide, we’ll explain why WordPress emails fail, how to test them, and how to fix the problem step by step. We’ll compare your sending options in a table, and we’ll show the records that keep your email out of the spam folder.
Why WordPress Emails Do Not Send
By default, WordPress sends email with a function called wp_mail. The official wp_mail documentation explains that it uses the PHP mail function of your server unless something else is set up. That default method is simple, but it has several weaknesses.
Common causes
- Your host blocks or limits PHP mail, to stop spam from shared servers.
- Your emails are sent without a login, so receiving servers do not trust them.
- Your domain has no SPF, DKIM, or DMARC records, or the records are wrong.
- The From address does not match your domain, for example a free mailbox address used as the sender.
- The sending server has a poor reputation, because other sites on it send spam.
- A plugin conflict or a form setting stops the message before it is sent.
- The email goes to spam, and you do not see it.
- The recipient’s mailbox is full, or the address is wrong.
First, Find Out Where the Email Fails
An email passes through several stages. Find the stage where it fails, and you know what to fix.
| Stage | What can go wrong | How to check |
|---|---|---|
| 1. WordPress creates the email | A form or plugin setting blocks it | Test with a plain test email |
| 2. The server sends it | PHP mail is disabled or limited | Use an email log plugin |
| 3. The receiving server accepts it | It rejects mail that fails SPF, DKIM, or DMARC | Check the bounce message |
| 4. The mailbox places it | The message goes to spam | Check spam, and use a mail test tool |
Check the spam folder first
Before you change anything, check the spam and junk folders of the receiving address. Many sites do send email, and it ends up there. If you find your messages in spam, the problem is deliverability, and the sections on SPF, DKIM, and DMARC below are your fix.
Send a test email
Most SMTP plugins have a test email tool. Send a test to an address you can check, and note the result. Also send a test to an address on a different provider, because one provider may accept mail that another rejects.
Install an email log
An email log plugin records each email that WordPress tries to send, with its status. It shows whether WordPress created the email at all. If an email is not in the log, the problem is the form or plugin that should create it. If it is in the log with a failed status, the problem is in sending.
Check the Simple Things
Before you set up anything new, rule out these quick causes.
- The admin email in Settings, then General, is an address that exists and that you can read.
- The email address in your form’s notification settings is correct.
- The From address in the form matches your site’s domain.
- The form plugin is not set to save messages only, without sending.
- No other plugin is changing or blocking email.
- Your site has no plugin conflict. If you suspect one, read our guide on how to find which plugin is breaking your site.
The Main Fix: Send Email Through SMTP or an Email API
The most reliable fix is to stop using PHP mail, and to send your email through a real mail service. You do this with a plugin that connects WordPress to that service. You keep your current hosting.
What SMTP does
SMTP is the standard way to send email. Your site logs in to a mail server with a username and password, or with a key, and the server sends the message. Because the message is authenticated, receiving servers trust it more.
Sending options compared
| Option | How it connects | Good for | Things to know |
|---|---|---|---|
| Your own mailbox SMTP, for example from your domain email host | SMTP with login | Very small sites with a few emails a day | Daily sending limits, and a risk of being flagged if you send bulk mail |
| Google Workspace or Microsoft 365 | SMTP or API with app login | Sites that already use these for email | Setup needs care, and sending limits apply |
| Transactional email service | API or SMTP with a key | Shops, membership sites, and busy forms | Has a free or paid plan depending on volume |
| Your host’s SMTP relay | SMTP | Sites on hosts that provide a relay | Depends on the host’s rules and reputation |
| Default PHP mail | None | Nothing important | Often blocked, and often goes to spam |
For most sites, a transactional email service is the best choice. These services are made to deliver system emails such as form notices, receipts, and password resets. Check the current pricing and free allowance on each provider’s page, because plans change.
Which ports to use
Use the port that your provider recommends. In general:
- Port 587 with TLS is the most common and the best default.
- Port 465 with SSL is a good second choice.
- Port 443 is used by some providers’ API methods, which work over the normal web port.
- Avoid port 25. Many hosts and networks block it, and it is not meant for sending from a website.
If your host blocks the SMTP ports, use a provider that offers an API over HTTPS. This works because it does not need an SMTP port.
How to Set Up SMTP in WordPress
The steps are similar for most plugins.
- Back up your site, and choose a mail provider.
- Create an account with the provider, and add your domain.
- Add the DNS records that the provider asks for. These usually include SPF and DKIM.
- Install an SMTP or email API plugin from the WordPress repository.
- Enter the provider details: the host, port, encryption, username, and password, or the API key.
- Set the From email to an address on your own domain, and set a clear From name.
- Turn on the option that forces this From address, so that other plugins do not override it.
- Send a test email, and check the result.
- Turn on email logging so that you can see what happens next.
- Test your contact form, your password reset, and, if you have one, your order email.
Keep your keys and passwords private, and do not paste them in a public support post. If your host lets you store secrets in wp-config.php, use that.
Fix Email Authentication: SPF, DKIM, and DMARC
Even with SMTP, your email can land in spam if your domain does not prove that it allows the sender. Three DNS records do this.
| Record | What it does | Where you add it |
|---|---|---|
| SPF | Lists the servers that may send email for your domain | A TXT record in your domain’s DNS |
| DKIM | Adds a signature that proves the message was not changed | A TXT or CNAME record, as your provider tells you |
| DMARC | Tells receivers what to do with mail that fails SPF and DKIM, and sends you reports | A TXT record named _dmarc |
SPF
You can have only one SPF record for a domain. If you already have one, add your new provider to it. Do not create a second one, because two SPF records cause a failure. Providers give you the exact text to include.
DKIM
Your provider gives you a key or a set of records. Add them exactly as shown, then use the provider’s verify button. DKIM is what makes your messages look like they really come from you.
DMARC
Start with a monitoring policy, which asks receivers to report but not to reject. Read the reports for a few weeks, and fix any legitimate sender that fails. Then you can move to a stricter policy. Large mailbox providers publish sender rules, and they expect authenticated mail, so this step matters more every year.
Use the same domain everywhere
The domain in your From address should be the domain that you authenticate. If you send as an address at your domain, but authenticate a different domain, receivers may treat the message as suspicious. Align them.
Contact Form Emails Not Arriving
Contact forms have extra pitfalls.
- Do not use the visitor’s email as the From address. Your server is not allowed to send for that domain, and the message fails authentication. Use your own From address, and put the visitor’s address in the Reply-To field.
- Check that the form’s notification is turned on, and that its recipient is correct.
- Check that the form is not blocked by an anti-spam rule or a captcha that is set up wrongly.
- Check the form’s saved entries. If the entries exist, the form works and the email is the problem.
Password Reset and Order Emails
WordPress system emails, such as password resets and new user notices, use the same wp_mail function. Once you set up SMTP, they use it too. For a shop, also check the shop plugin’s own email settings, and send a test order to confirm the receipt arrives.
If a user says that the reset email does not arrive, ask them to check spam, and check your email log. Also check that their address is correct in their profile.
Emails Still Not Sending? Troubleshooting Steps
- Read the log. A failed status usually gives a reason, such as a wrong password, a blocked port, or an unverified domain.
- Check that the plugin’s connection test passes.
- Switch the port and encryption to the other recommended pair.
- Check that your host does not block outgoing SMTP, and ask them if you are unsure.
- Turn off other plugins that may change email, and test again.
- Check your provider’s dashboard for blocked or bounced messages.
- Use a mail testing tool to check your SPF, DKIM, and DMARC results.
- Check that your domain’s DNS has changed, because records can take some time to spread.
If your site also feels slow or a recent update changed how emails work, read our guide on what to do when your WordPress site breaks after an update.
How to Keep Your Email Out of Spam
- Authenticate your domain with SPF, DKIM, and DMARC.
- Send from an address on your own domain.
- Use a reputable email service, not default PHP mail.
- Keep email content clear and honest, without spam words or heavy images.
- Send system emails and marketing email from different addresses or services, so that marketing problems do not hurt your receipts.
- Remove invalid addresses and never buy lists.
- Watch bounce and complaint rates in your provider’s dashboard.
- Avoid sudden large spikes in volume from a new account.
How to Read a Bounce Message
When an email fails, the receiving server often sends back a bounce message. Most site owners ignore it, but it names the cause in plain words.
| Bounce wording | What it usually means | What to do |
|---|---|---|
| Authentication failed, or SPF fail | The sending server is not listed in your SPF record | Add your mail provider to SPF |
| DKIM signature missing or invalid | The message was not signed, or the key is wrong | Re-add the DKIM records and verify |
| Rejected by DMARC policy | SPF and DKIM do not align with the From domain | Match the From address to the authenticated domain |
| Mailbox full | The recipient has no space | Ask the recipient to free space |
| User unknown, or no such address | The address is wrong | Correct the address |
| Blocked, or listed on a blocklist | The sending IP has a poor reputation | Use a reputable service with its own clean IPs |
| Too many connections, or rate limit | You sent too fast or too much | Slow down, or move to a higher plan |
Bounces go to the address in the Return-Path or the From field. If you never see them, set up your mail provider’s dashboard, because it keeps a record of each bounce.
Using an Email Log Well
An email log is the best tool for ongoing problems. Set it up once, and it pays back each time something fails.
What to look for
- The date and time of each message.
- The recipient, the subject, and the From address.
- The status: sent, failed, or queued.
- The error text for failed messages.
- Which plugin created the message.
How long to keep logs
Logs hold email content and addresses, so treat them as private data. Keep them long enough to solve problems, for example a few weeks, and delete older entries. If your site serves visitors in places with strict privacy rules, check what you must tell users about stored data.
Sending Limits and Volume
Every sending method has limits. If your site sends many emails, you will reach them.
- Shared hosts often cap the number of emails per hour. When you pass the cap, extra messages are dropped or delayed.
- Mailbox providers cap the number of messages per day for each account.
- Transactional services have monthly plans, and each plan has a volume limit.
- New accounts and new domains often have lower limits until they build a reputation.
If you send newsletters or large bulk messages, do not send them from WordPress with the same service that sends your receipts. Use a dedicated newsletter service, so that a complaint about a newsletter does not block a password reset.
A Quick Look at Different Types of WordPress Email
Different parts of your site create different emails, and each has its own settings.
| Email type | Created by | Where to check |
|---|---|---|
| Password reset and new user notices | WordPress core | Settings, General, and your SMTP plugin |
| Contact form notices | A form plugin | The form’s notification settings |
| Order receipts and shipping notices | A shop plugin | The shop’s email settings |
| Comment notices | WordPress core | Settings, Discussion |
| Membership and course emails | A membership plugin | The plugin’s email tab |
| Update and security notices | WordPress core | The admin email in Settings, General |
Set up SMTP first, since all of these use it. Then check each type, because some plugins have their own sender settings that can override yours.
Privacy and Safety Tips for Email Setup
- Never store a mailbox password in a place that other users can read. Prefer an API key with limited rights.
- Use a separate sender account for the website, so that a leak does not expose your personal mailbox.
- Turn on two-step login for your mail provider account.
- Rotate keys if you think that one has leaked.
- Do not put passwords or private data in email bodies, since email is not private by design.
- Use TLS or SSL, and never send over an unencrypted connection.
Test Checklist After You Fix Email
Run each of these tests after any email change, such as a new plugin, a new host setting, or a DNS change.
- Send the SMTP plugin’s test email to two different providers.
- Submit your contact form, and check that the message arrives in the inbox, not in spam.
- Use the password reset on a test user, and check the link.
- If you sell products, place a test order and check the receipt.
- Open the email log, and confirm that all messages show a sent status.
- Check your provider’s dashboard for bounces and complaints.
- Run a mail testing tool, and check that SPF, DKIM, and DMARC all pass.
- Check again after a few days, to catch problems that appear later.
What to Do If You Have Already Lost Emails
If you find that emails have not been arriving for a while, you can still recover some of the information.
- Check your form plugin’s saved entries. Many form plugins keep a copy of each submission in the database, even when the email fails.
- Check your shop’s order list, since orders are saved even when the receipt email fails.
- Check your spam folder for older messages.
- Check your server’s mail logs, which your host may keep for a short time.
- Contact people who submitted forms, and apologize for the delay, once you have fixed the problem.
After you fix the issue, make a habit of checking one test message each month. Email can break again after a plugin update, a DNS change, or a host change, and a monthly test finds it quickly.
Why Your Host May Block Email
It helps to know why default mail fails, so you do not blame your site.
On a shared server, one hacked or careless site can send thousands of spam messages. That damages the reputation of the server’s address, and then every site on it has trouble. To protect itself, a host may block PHP mail, limit how many messages each account can send, or block the outgoing SMTP ports.
This is a reasonable rule, and it is not a sign that your host is poor. It does mean that you should not rely on the server’s default mail for anything that matters. When you send through a separate service, your messages leave from addresses that have their own reputation, and your host’s policy no longer affects you.
If your host blocks the usual SMTP ports, ask them which ports are open, or choose an email service with an HTTPS API. Both keep your current hosting in place.
How Long Do DNS Changes Take?
After you add SPF, DKIM, or DMARC records, the change can take from a few minutes to a day to reach all receivers. If your provider says that a record is not found, do these checks before you change anything.
- Check that the record name is exactly as the provider shows. Some DNS panels add your domain name automatically, so a full name can end up doubled.
- Check that the record type is correct, for example TXT where TXT is required.
- Check that you did not add a second SPF record.
- Remove extra quotation marks or spaces that your panel may have added.
- Wait, and then run the provider’s verify button again.
If your domain uses a separate DNS service in front of your host, add the records there, not in your hosting panel. The records only work at the place where your domain’s name servers point.
Which Setup Should You Choose?
A short rule helps most site owners decide.
- A small blog with a few form messages a week: a transactional service on a free plan, or your domain mailbox over SMTP.
- A business site with many leads: a transactional service with logging, plus SPF, DKIM, and DMARC.
- A shop or membership site: a transactional service on a paid plan, with a separate service for marketing email.
- A site where you cannot use SMTP ports: a service with an HTTPS API.
Whatever you choose, test it, log it, and check it again every month.
Frequently Asked Questions (FAQs)
Why are my WordPress emails not sending?
Usually because WordPress uses PHP mail, which many hosts block or limit, and because the domain has no authentication records. Sending through an SMTP or email API service fixes most cases.
Do I need to change my hosting to fix email?
No. You keep your host and send email through a separate mail service with a plugin.
Why do my WordPress emails go to spam?
Receivers do not trust unauthenticated mail. Set up SPF, DKIM, and DMARC, send from your own domain, and use a reputable service.
What is the best port for WordPress SMTP?
Port 587 with TLS is the usual choice. Port 465 with SSL also works. Avoid port 25.
Why does my contact form say it sent, but I get nothing?
The form created the message, but the server or the receiver dropped it. Check spam, use an email log, and switch to SMTP or an email API.
Can I use my Gmail address to send from WordPress?
You can use a Google account with the right login method, but daily limits apply, and the From address must match what you authenticate. A transactional service is a better fit for a busy site.
How do I test whether WordPress can send email?
Use the test email tool in your SMTP plugin, and send to two different providers. Then check the log and the spam folder.
What is the difference between SPF, DKIM, and DMARC?
SPF lists who may send for your domain, DKIM signs each message, and DMARC tells receivers what to do when the checks fail.
Do I need a plugin for SMTP?
Yes, in most cases. A plugin connects WordPress to your mail service, and it adds logging and test tools.
Can someone set this up for me?
Yes. If you prefer to hand the setup to an experienced person, you can get WordPress management and troubleshooting help through this Fiverr gig.
Final Thoughts
WordPress emails fail because the default sending method is weak, not because your site is broken. Replace PHP mail with an SMTP or email API connection, add SPF, DKIM, and DMARC records for your domain, and log your messages so that you can see what happens.
Test each type of email after the change: form notices, password resets, and, if you run a shop, receipts. Once the setup works, check your logs from time to time. A short test now saves you from missing a message that matters.

