WordPress not sending emails: contact forms and WooCommerce orders
By Michael Broadbridge. Last checked 14 November 2026 on WordPress 7.1, WooCommerce 11.3.
Short answer
By default WordPress sends email through the server’s PHP mail function, from an address such as wordpress@yourdomain, with nothing to prove the message is genuine, so inboxes often reject it. Install an SMTP plugin, connect it to a proper mail service, use a From address on your own domain, add SPF, DKIM and DMARC records, then send a test.
Symptoms
- A contact form shows its success message, but no email reaches the inbox.
- WooCommerce new order notifications stop arriving, or customers say they had no order confirmation.
- Password reset emails from the login page never arrive.
- Emails arrive in spam, or only reach some addresses.
- Email stopped without any change to the website.
Causes, most likely first
The site sends through PHP mail
WordPress hands every email to PHPMailer, which uses the server’s PHP mail function unless a plugin changes it. The message leaves a web server with no login behind it, so receiving mail servers reject it or file it as spam. Some hosts limit or block this kind of mail altogether.
The From address is not on your domain
If no From address is set, WordPress uses wordpress@ followed by your domain. Forms that send as the visitor’s own address, or a WooCommerce From address on gmail.com, look forged to the receiving server.
No SPF, DKIM or DMARC records
Gmail requires every sender to have SPF or DKIM, and senders of more than 5,000 messages a day to have SPF, DKIM and DMARC. Mail from a domain with none of them is far more likely to be refused.
The WooCommerce email is off or goes to the wrong address
Each WooCommerce email can be disabled on its own, and the shop’s notifications go to the address in that email’s Recipient(s) field, which is often an old address.
The order never reached a status that sends email
WooCommerce does not send emails for orders left on Pending payment. If paid orders sit on that status, the payment gateway is the problem, not email.
How to fix it
Find out where the email stops
A success message on a form, or an order in WooCommerce, only means WordPress tried to send. Work out whether the email was created and handed over, or handed over and then rejected.
- Check the spam and filtered folders of the address that should receive the email.
- For WooCommerce, open the log with the source transactional-emails. Each entry says Sent, Failed, Disabled or Skipped. Sent means WooCommerce handed the email to the mail system, so the problem is delivery.Menu:
WooCommerce > Status > Logs - If WooCommerce shows Disabled, the email is switched off. If it shows Skipped, something it needs, such as a recipient, is missing.
- If there are no entries at all, check the logging settings on the same screen are switched on and not hiding lower level entries.
- Check the status of an order that should have sent an email. Pending payment orders send no email.Menu:
WooCommerce > Orders
Check the form’s email settings
Contact Form 7, WPForms, Gravity Forms and similar plugins all hand their email to WordPress to send, so the same delivery fix applies to each. Their own settings are worth checking first.
- In Contact Form 7, open your form and click the Mail tab.Menu:
Contact > Contact Forms - Check the To field holds the address that should receive enquiries.
- Set the From field to an address on your website’s own domain, for example website@yourdomain.co.uk. Contact Form 7 shows the warning "Sender email address does not belong to the site domain." when it is not.
- To reply straight to the visitor, put Reply-To: [your-email] in the Additional headers box instead of using the visitor’s address as the From address.
- In WPForms, open the form, go to Settings, then Notifications, and check Send To Email Address, From Email and Reply-To Email Address in the same way.
- Save the form.
Check WooCommerce’s email settings
- Open the list of email notifications, such as New order, Processing order and Completed order.Menu:
WooCommerce > Settings > Emails - Click Manage next to an email that is going missing and check the Enable/Disable setting is ticked.
- For emails sent to the shop, such as New order, Cancelled order and Failed order, check the Recipient(s) field. Separate several addresses with commas. By default it is the Administration Email Address under Settings, then General.
- Below the list of emails, set the "From" address to an address on your own domain. WooCommerce recommends this for deliverability.
- Use Send a test email in the Email Preview section to send yourself a copy.
Send through SMTP with a proper mail service
SMTP is the standard way to send email through an authenticated account, so the receiving server can see the message is genuine. An SMTP plugin makes every WordPress email go out this way, including forms, WooCommerce orders and password resets. WP Mail SMTP and FluentSMTP are widely used.
The plugin needs a mail service to send through. That can be a transactional email service such as Brevo, Mailgun, Postmark or SendGrid, or the Google Workspace or Microsoft 365 account you already use for business email.
- Install and activate the SMTP plugin from the Plugins screen and follow its setup wizard.
- Choose your mail service and connect it. Most services use an API key, a long code you copy from your account with the mail service, rather than an email password.
- Set the From Email to an address on your domain. In WP Mail SMTP, tick Force From Email so every plugin uses that address.
- Save the settings.
Treat an API key like a password. Paste it into the plugin yourself and do not send it to anyone by email. In WP Mail SMTP, the Microsoft one-click setup and Amazon SES are paid features.
Add SPF, DKIM and DMARC records
These are records in your domain’s DNS, the settings that tell the internet where your website and email live. SPF lists the services allowed to send email for your domain. DKIM adds a signature to each message so the receiver can check it really came from an approved sender. DMARC tells receivers what to do with mail that fails those checks, and Google accepts a DMARC policy of none to start with.
Your mail service gives you the exact SPF and DKIM records. They go in the DNS settings wherever your domain’s nameservers point, usually your domain registrar, your host or Cloudflare. Most services show a Verified status once they find the records.
A domain can only have one SPF record. If one already exists, add the new service to it instead of creating a second record. Take a screenshot of your DNS settings before changing anything, as a mistake here can stop your normal email working.
Test that it works
- In WP Mail SMTP, open the Email Test tab and send a test to an address you can check. Other SMTP plugins have a similar test.Menu:
WP Mail SMTP > Tools - Submit the real form on the live page, using a different email address from the one that receives enquiries.
- Place a test order and check that both the customer email and the New order email arrive.
- Check the inbox, the spam folder and any filtered folders. Test with both a Gmail address and an Outlook or Microsoft 365 address if you can, as they filter differently.
If that didn’t work
The form fails before any email is created
If the form shows an error on screen, the problem is in the form, not delivery. Contact Form 7, for example, shows the same error for a failed send and for a submission it has marked as spam.
A plugin conflict stops WooCommerce emails
WooCommerce suggests checking the logs for fatal errors, then testing with only WooCommerce and a default theme active, ideally on a staging copy.
Your host blocks outgoing mail
Some hosts limit or block outgoing mail from websites. Your host’s support can tell you what is allowed.
Keep a record of every email
Email can fail again, so keep a copy on the site as well. For Contact Form 7, the free Flamingo plugin saves every submission in the dashboard. WooCommerce keeps its transactional-emails log under WooCommerce, then Status, then Logs. FluentSMTP includes an email log for free, and WP Mail SMTP offers one in its paid version. A log shows every message the site tried to send and whether the mail service accepted it. WooCommerce’s log does not cover WordPress password reset emails, so an SMTP plugin’s log is the place to check those.
When to get help
Stop and ask if you are unsure about editing DNS records, since a mistake there can interrupt all of your business email, or if the test email reports success but messages still never arrive. It is also worth asking when enquiries or order emails have been going missing for some time and you need to find out what was lost.
What a developer would check
- The SMTP plugin’s email log and the mail service’s own activity log, to see whether each message was accepted and what came back.
- The domain’s SPF, DKIM and DMARC records against the mail service’s instructions.
- The WooCommerce transactional-emails and fatal-errors logs.
- Whether the host blocks or limits outgoing mail.
Describe the problem in your own words and WebFixed gives you an instant fixed quote. Nothing is charged until you accept it.
Related questions
- Why did my site stop sending emails when I changed nothing?
- Email providers have tightened their rules on unauthenticated mail, and hosts change their mail settings from time to time. A site that relied on PHP mail can stop being delivered without any change on the website.
- Does an SMTP plugin fix WooCommerce order emails too?
- Yes, for delivery. Order confirmations, new order notifications and password resets all go through the same WordPress mail function. Check in WooCommerce that each email is enabled and has the right recipient as well.
- The form says the message was sent, so where did it go?
- The success message only means WordPress handed the email over. It does not confirm delivery. The message was most likely rejected or filtered by the receiving mail provider, which SMTP, SPF, DKIM and DMARC put right.
Written by Michael Broadbridge, Founder of Webgro. First published 21 September 2026. Last checked 14 November 2026 on WordPress 7.1, WooCommerce 11.3.