Your WordPress site says a form was submitted successfully, but no email arrives.
Maybe password reset emails are missing. Contact form notifications never reach your inbox. WooCommerce messages disappear. Or WordPress reports that an email was sent even though you never receive it.
This is a common WordPress problem, and the cause is often not the form itself.
QUICK ANSWER
If WordPress is not sending email, first confirm that the website actually created the message. Then check the recipient address, spam folder, notification settings, sender address, and SMTP configuration. If WordPress email is still unreliable, connect the site to an authenticated SMTP or email service and send a test email before troubleshooting the form itself.
Why Is WordPress Not Sending Email?
WordPress uses its wp_mail() function when the core system, themes, or plugins need to send email.
However, successfully processing an email request does not automatically mean that the message reached the recipient’s inbox.
The failure can happen at several different points:
- The form never created a notification
- The recipient email address is incorrect
- The server cannot send mail reliably
- The sender address fails authentication
- The SMTP connection is misconfigured
- The message is rejected or sent to spam
- A plugin or security rule blocks the email
The fastest way to fix the problem is to identify exactly where the delivery process stops.
1. Confirm That WordPress Actually Received the Form Submission
Start by separating two different problems:
- Form submission problem
- Email delivery problem
A contact form can display a successful submission message even when the notification email never arrives.
If your form plugin stores entries, open its submissions or entries section and check whether the test message appears there.
For example, many form plugins have a section such as:
Forms → Entries
If the entry exists, the form itself probably worked. Your next step should be troubleshooting the email notification and delivery system.
If there is no entry at all, investigate the form configuration, spam protection, JavaScript errors, or plugin conflicts before changing SMTP settings.
2. Check the Recipient Email Address and Spam Folder
Before installing or changing anything, check the basics.
Open the form’s email notification settings and confirm that the recipient address is correct.
Look for settings such as:
- Send To
- Notification Email
- Recipient
- Admin Email
Then check:
- Inbox
- Spam
- Junk
- Promotions
- Quarantine folders if you use a business email service
Also try sending the notification to another email address.
If one provider receives the message and another does not, the problem may be related to filtering or sender authentication rather than WordPress itself.
3. Check the Form’s Email Notification Settings
If your contact form submission is stored but no email arrives, open the form’s notification settings.
Check the following fields carefully:
- Send To: your real inbox
- Subject: a clear notification subject
- From Name: your website or business name
- From Email: an address allowed by your mail provider
- Reply-To: preferably the visitor’s email field when appropriate
One common mistake is placing the visitor’s email address directly in the From Email field.
This can cause authentication problems because your website is trying to send a message that appears to come from an address it does not control.
A safer structure is:
From Email: an authenticated website or mail account
Reply-To: the visitor’s submitted email address
This allows you to reply directly to the visitor without making the outgoing message appear to originate from their account.
4. Send a WordPress SMTP Test Email
Before testing your contact form repeatedly, test the site’s email system directly.
If you use an SMTP plugin, find its email test feature.
Enter an email address you can access and send a test message.
There are two important outcomes.
If the SMTP test email arrives
Your mail connection is working.
The remaining problem is more likely to be:
- Form notification settings
- Recipient configuration
- A specific plugin
- Spam filtering
- A conditional notification rule
If the SMTP test email does not arrive
Do not keep changing the contact form.
Focus on the mail connection itself, including:
- SMTP provider
- Authentication
- OAuth connection
- Sender email
- DNS authentication
- Hosting restrictions
This simple test can prevent a lot of unnecessary troubleshooting.
5. Configure Authenticated SMTP
If WordPress email is unreliable, an authenticated mail connection is usually more dependable than relying on the server’s default mail configuration.
Popular WordPress SMTP solutions can connect WordPress to services such as:
- Gmail or Google Workspace
- Microsoft 365
- Brevo
- SendGrid
- Amazon SES
- Mailgun
- Your hosting provider’s SMTP server
The exact setup depends on the service you choose.
In general, you will need either:
- SMTP server credentials
or:
- API or OAuth authorization
After connecting the provider, always send a test email before assuming the setup is complete.
TIP:
Do not judge an SMTP setup only by whether the plugin says “connected.” Send a real test email and confirm that it actually arrives in the destination inbox.
6. If You Use Gmail, Check the OAuth Connection
Gmail and Google Workspace integrations commonly use OAuth rather than a normal account password.
A typical Gmail SMTP or API connection may require:
- Google Cloud project
- Gmail API enabled
- OAuth consent configuration
- OAuth Client ID
- Client Secret
- Authorized redirect URI
- Google account authorization
If the connection returns an OAuth error, check whether the correct Google account is authorized.
If the OAuth application is still in testing mode, the account being used may also need to be allowed as a test user.
After completing authorization, return to WordPress and send another test email.
IMPORTANT:
Treat Client Secrets, SMTP passwords, API keys, and OAuth credentials like passwords. Do not publish them in screenshots, support forums, blog posts, or public documentation.
7. Make Sure the From Email Matches Your Mail Setup
The sender address is one of the most important email delivery settings.
If WordPress is authenticated to send from one account but your form uses a completely different address in the From field, receiving servers may distrust the message.
For example, if your SMTP connection authenticates:
notifications@example.combut the form tries to send as:
random-address@gmail.comthe mismatch can create delivery or authentication problems.
When possible, use an authenticated sender address that belongs to the account or domain configured for sending.
Then use the form visitor’s address only in the Reply-To field.
8. Check SPF, DKIM, and DMARC
If you send email from your own domain, email authentication becomes increasingly important.
The three terms you will see most often are:
- SPF – identifies servers or services authorized to send mail for your domain
- DKIM – adds a cryptographic signature that helps receiving servers verify the message
- DMARC – tells receiving servers how to handle messages that fail authentication and alignment checks
These records are usually added in your domain’s DNS settings.
If your email provider gives you SPF, DKIM, or DMARC records, copy them exactly as instructed.
Do not create multiple conflicting SPF records for the same domain.
After making DNS changes, allow time for the new records to propagate and then test email delivery again.
9. Check Plugins, Security Tools, and Hosting Restrictions
If SMTP works but a specific form still does not send notifications, investigate the WordPress environment.
Possible causes include:
- Spam protection blocking the form submission
- Security plugin rules
- Conditional form notifications
- Plugin conflicts
- Incorrect form shortcodes or field mappings
- Hosting restrictions on outgoing mail
- Rate limits imposed by your email provider
If the problem began immediately after installing or updating a plugin, that change is an important clue.
Temporarily disabling suspected plugins can help isolate the problem, but do this carefully on a production website.
If no WordPress setting explains the failure, check your hosting provider’s mail logs or contact the host and ask whether outgoing email connections are being blocked.
A Fast Troubleshooting Order
If WordPress email is not working, use this order instead of changing random settings:
- Submit a test form
- Check whether the entry was stored
- Confirm the recipient email
- Check spam and junk folders
- Review From Email and Reply-To
- Send an SMTP test email
- Fix SMTP or OAuth if the test fails
- Check SPF, DKIM, and DMARC if using your own domain
- Submit the form again
- Confirm the notification actually arrives
This process tells you whether the failure is in the form, WordPress, the mail connection, DNS authentication, or the receiving inbox.
Quick Checklist
- Contact form entry is stored
- Recipient address is correct
- Spam folder has been checked
- Email notification is enabled
- From Email is valid
- Reply-To uses the visitor email when appropriate
- SMTP connection is authenticated
- SMTP test email arrives
- SPF or DKIM is configured when required
- Plugin and security conflicts have been checked
Frequently Asked Questions
Why does my WordPress form say “success” but I receive no email?
The form submission and the email notification are separate processes. The form may successfully save the visitor’s message while the notification fails later because of email configuration, authentication, spam filtering, or SMTP problems.
Does WordPress need SMTP to send email?
WordPress can send email without a separate SMTP plugin in some hosting environments. However, authenticated SMTP or an email API can provide more reliable delivery and clearer troubleshooting when the default mail configuration is unreliable.
Why does the SMTP test work but my contact form still does not send email?
If a direct SMTP test succeeds, your email connection is probably working. Check the contact form’s notification settings, recipient address, From Email, Reply-To field, conditional rules, spam protection, and plugin configuration.
Why are WordPress emails going to spam?
Possible causes include poor sender reputation, missing email authentication, sender-address mismatches, message content, or recipient filtering. If you send from your own domain, review SPF, DKIM, and DMARC settings with your email provider.
Can Gmail be used to send WordPress emails?
Yes. WordPress SMTP plugins can connect to Gmail or Google Workspace. Depending on the plugin, the connection may use Google OAuth and the Gmail API instead of a normal Gmail password.
Final Thoughts
When WordPress is not sending email, avoid changing every setting at once.
Start by confirming whether the form submission exists. Then test the email system separately.
If the SMTP test fails, fix email delivery first.
If the SMTP test succeeds but the form notification does not arrive, focus on the form’s notification settings and plugin configuration.
The key is to identify where the message stops instead of treating every missing email as the same problem.