A contact form that looks fine but never reaches your inbox is one of the quietest problems a website can have. Nothing crashes and the site keeps passing every uptime check. Meanwhile, WordPress is not sending emails that matter: new leads, WooCommerce order confirmations, password reset links and admin alerts either vanish or land in a spam folder nobody checks.
The good news is that this problem has a clear cause and a lasting fix. Below we cover why WordPress email fails, what Gmail, Yahoo and Microsoft now expect, how to test delivery, and how to set up WordPress SMTP with proper SPF, DKIM and DMARC records so the problem stays fixed.
Why WordPress Emails Go Missing
Every core email, and most plugin emails, goes through one function called wp_mail(). It builds the message and hands it to PHPMailer, which by default uses PHP’s built-in mail() function on your server. The WordPress developer reference for wp_mail() is very direct about what that means: a true return value only tells you the request was processed without errors, not that anyone received the email.
That gap is where messages disappear. When PHP mail() runs, your web server acts as the sender. It usually has no login to a real mailbox, no DKIM signature, and often no SPF record that lists it as an allowed sender for your domain. To Gmail or Outlook, that looks like spoofed mail, so it goes to spam, gets rejected, or is quietly dropped.
Shared hosting makes this worse. Dozens of sites can share one outgoing IP address, so if one of them sends spam or gets hacked, your legitimate form emails inherit the bad reputation. Some hosts respond by limiting or blocking outgoing mail entirely, which means wp_mail() can report success while the host throws the message away.
The default sender address adds one more weak point. If no plugin sets a From address, WordPress uses wordpress@ followed by your domain. That mailbox usually does not exist, and the WordPress source code itself notes that some hosts block outgoing mail from that address for exactly this reason. Add a plugin conflict after an update or a security plugin blocking outbound connections, and mail can fail without a single visible error.
None of this means WordPress is broken. The default setup was simply never designed for modern inboxes. If you want a wider view of other silent failures, our guide to common WordPress errors and how to fix them covers the problems that tend to appear alongside email issues.
How to Test Where Your Emails Are Going
Before changing settings, find out where the mail is breaking. A few simple tests tell you whether WordPress is generating the email, whether it leaves the server, and what the receiving inbox thinks of it. Run them in this order:
- Send a real test. Submit your own contact form, trigger a password reset, or place a test order. Use Gmail, Outlook.com and business-domain addresses, since each filters differently.
- Check spam and junk folders. If the message arrives there, WordPress is sending but your domain is failing email authentication or reputation checks. If it does not arrive anywhere, the problem is earlier.
- Read the message headers. In Gmail, open the message and choose “Show original”. Look for the SPF, DKIM and DMARC results. A “fail” or “none” next to any of them points straight to your DNS setup.
- Turn on a mail log. A mail logging plugin records every email WordPress tries to send. If the form submission never appears in the log, the form plugin or a conflict is the issue, not delivery.
- Check the server and plugin logs. WordPress fires a wp_mail_failed action when PHPMailer throws an error, and many SMTP plugins capture it. Host mail logs, if available, show whether the next server accepted it.
Once you know which stage fails, the fix becomes obvious. Missing from the log means a site problem, present in the log but absent from the inbox means a delivery problem, and present in spam means an authentication or reputation problem. Most sites need the same cure.
The Lasting Fix: An SMTP Plugin and a Real Sending Service
The reliable fix is to stop letting your web server act as a mail server. Instead, you install an SMTP plugin that reroutes wp_mail() through an authenticated account with a proper email provider. WordPress creates the message as before, but delivery runs through infrastructure with a login, a DKIM signature and its own reputation.
There are three common ways to do this, and the right choice depends on how much mail the site sends and how important each message is. The table below compares them without pointing to any single vendor.
| Approach | How it works | Good fit for | Watch out for |
|---|---|---|---|
| Host mail (PHP mail) | Server sends directly with no login | Nothing critical; temporary use only | Shared IP reputation, no DKIM, silent drops |
| Host SMTP mailbox | SMTP login to a mailbox at your host | Low-volume sites on a reputable host | Still tied to host reputation and limits |
| Google Workspace or Microsoft 365 SMTP | Plugin signs in to your business mailbox | Small sites already using these mailboxes | Sending limits, app passwords or OAuth setup, mixing site mail with staff mail |
| Transactional service (for example Postmark, Mailgun, Amazon SES, Brevo) | Plugin sends through the service’s API or SMTP | Stores, membership sites, lead-driven sites | Domain verification and DNS records required; check current plans and limits |
For most business sites, a transactional email service is the most dependable option. They are built for receipts, alerts and form notifications, with delivery logs, bounce reports and clear DNS instructions. Plans and limits change often, so check each provider’s current pricing before you commit.
Using Google Workspace or Microsoft 365 can work well for a small site, especially if you already pay for those mailboxes. The trade-off is that site mail shares limits and reputation with your team’s email. Whatever you choose, use a dedicated sender address on your own domain, such as notifications@ or forms@, and never a free Gmail or Yahoo address.
The final step is to send a test email through the plugin and confirm it lands in the inbox with SPF, DKIM and DMARC all showing “pass”. That depends on your DNS, where many setups are left half finished.
SPF, DKIM and DMARC: What Gmail, Yahoo and Microsoft Expect
The big mailbox providers have tightened their rules, and those rules apply to your website’s email too. Google’s email sender guidelines state that, starting February 1, 2024, everyone sending to Gmail accounts must meet a baseline: set up SPF or DKIM, have valid forward and reverse DNS for sending servers, use TLS, and keep reported spam rates below 0.3%. Senders of more than 5,000 messages a day to Gmail must also set up SPF, DKIM and DMARC together, with the From domain aligned to one of them.
Yahoo followed the same path. Its sender requirements began enforcement in February 2024, with SPF or DKIM required for all senders and SPF, DKIM and a valid DMARC policy required for bulk senders. Microsoft joined in 2025: its Outlook announcement for high-volume senders says that from May 5, 2025, domains sending over 5,000 emails a day to Outlook.com, Hotmail and Live addresses must pass SPF, DKIM and DMARC, with non-compliant mail routed to Junk and later rejected.
Most WordPress sites send far fewer than 5,000 emails a day, so it is tempting to ignore this. That would be a mistake: Microsoft’s own FAQ says all senders benefit from these practices, and Google warns that unauthenticated messages may be marked as spam or rejected. Authentication is no longer an extra; it is the entry ticket.
Here is what each DNS record does and what a typical setup looks like. Values are examples; your provider gives you the exact ones.
| Record | What it does | Example DNS entry |
|---|---|---|
| SPF (TXT on yourdomain.com) | Lists the servers allowed to send for your domain | v=spf1 include:_spf.google.com include:spf.yourprovider.com ~all |
| DKIM (TXT or CNAME on a selector, such as s1._domainkey) | Adds a cryptographic signature that proves the message was not altered | v=DKIM1; k=rsa; p=MIIBIjANBgkq… (public key from your provider) |
| DMARC (TXT on _dmarc.yourdomain.com) | Tells receivers what to do when SPF or DKIM fails, and where to send reports | v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com |
A few details trip people up. A domain should have only one SPF record, so when you add a new sender you edit the existing record and add another include rather than creating a second one. Google’s guides for setting up SPF and setting up DMARC show the exact steps, and transactional services publish their own include values.
DMARC deserves a careful rollout. The DMARC.org overview explains how the policy builds on SPF and DKIM and how reports show you who is sending as your domain. Start with p=none, read the reports for a few weeks to make sure every legitimate sender passes, then move to quarantine and finally reject. Jumping straight to reject can block your own invoices if one service was never added.
The From Address Mistake in Contact Forms
Even with SMTP and DNS in place, a single form setting can still sink delivery. Many form plugins let you set the notification From address to a field value, so the email appears to come from the visitor and you can just hit reply.
The problem is that your server or SMTP service is now sending mail that claims to be from someone@gmail.com or someone@yahoo.com. Those domains publish strict DMARC policies, so receivers treat the message as spoofed and reject it or send it to spam. This is one of the most common reasons behind contact form emails not received, and it often starts the day a visitor with a Gmail address fills in the form.
The fix takes two minutes. Set the From address to a fixed address on your own domain, such as forms@yourdomain.com, and put the visitor’s email in the Reply-To field instead. You still reply with one click, and the message passes authentication because it really does come from your domain. While you are there, confirm the notification recipient is still correct.
Fixing WooCommerce Emails Not Sending
When WooCommerce emails are not sending, the cause is not always delivery. WooCommerce only sends an email when an order changes status, so a payment gateway that fails to move orders to Processing, or a plugin error during checkout, means no email is ever created. The official WooCommerce email FAQ recommends checking for fatal errors and ruling out conflicts with a default theme before blaming the mail server.
WooCommerce also gives you a built-in way to see what happened. It logs each transactional email attempt, so you can tell whether a message was sent, failed or never attempted. Work through these checks:
- Go to WooCommerce, then Settings, then Emails, and confirm the email type is enabled and the recipient field is correct for admin notifications.
- In the same screen, set the “From” address to one on your store’s domain, not a free Gmail or Yahoo address.
- Create a test order, then open WooCommerce, then Status, then Logs, and filter for the source named transactional-emails.
- If the log shows the email as sent but customers never get it, the problem is delivery, so move the store to SMTP with a transactional service and finish your DNS records.
- Remember that WordPress password resets and other admin emails are not WooCommerce emails, so check them in your SMTP provider’s logs or a mail logging plugin.
For a store, missing emails cost more than inconvenience. Customers without a confirmation contact support, open disputes or shop elsewhere. Email checks belong in regular WooCommerce maintenance alongside updates, checkout tests and backups.
Example: A Contact Form That Lost Leads for Weeks
Here is an illustrative scenario built from a very common pattern. A local service business runs a WordPress site with a quote request form, and the office receives a few leads every day. Then the leads slow down and eventually stop. The owner assumes it is a seasonal dip and increases ad spend to compensate.
About five weeks later, a customer calls and mentions that they filled in the form twice and never heard back. The form plugin’s entries screen shows dozens of submissions over those weeks, all real leads, and not one notification reached the office inbox.
The cause turned out to be a combination of small problems. The host had quietly started limiting outgoing PHP mail after its shared IP landed on a block list. The form’s From address was set to the visitor’s own email, so every message from a Gmail user failed DMARC. On top of that, the domain had an SPF record that only listed the old email host, not the web server or any SMTP service. Together, these stopped almost everything.
The repair took less than a day. The team installed an SMTP plugin connected to a transactional service, verified the domain, and added the provider’s DKIM records. They merged two conflicting SPF records into one, published a DMARC record at p=none with reporting turned on, and changed the form to send from forms@ the company’s domain with the visitor in Reply-To. Tests to Gmail, Outlook and the office mailbox all passed authentication.
The lesson is not only technical. The site never went down, so no uptime alert ever fired. Uptime checks tell you the site loads; they do not tell you that forms deliver. Our guide to WordPress uptime monitoring covers that layer; form delivery needs its own regular test.
Checklist for Reliable WordPress Email
Use this checklist when you set up a new site, after a migration, or any time you suspect messages are going missing.
- Install an SMTP plugin and connect it to a mailbox or transactional service, not PHP mail.
- Use a sender address on your own domain for all site and form notifications.
- Set form notifications to send from your domain, with the visitor in Reply-To.
- Publish one SPF record that includes every service sending for your domain.
- Turn on DKIM signing with each provider and add its DNS records.
- Publish a DMARC record, start at p=none, review reports, then tighten the policy.
- Send test emails to Gmail, Outlook and your own domain and check the headers for SPF, DKIM and DMARC passes.
- Keep a mail log active so you can prove whether an email was sent.
- Test WooCommerce emails with a real test order after updates and gateway changes.
- Retest forms monthly and after every plugin, theme, DNS or hosting change.
If you tick every item, your site email moves from “probably working” to something you can actually verify. The last point matters most, because email setups usually break months later after a change nobody linked to email.
How Webueno Handles Email Delivery Problems
When a client tells us forms or order emails have stopped arriving, we treat it as a troubleshooting ticket with a clear process rather than guesswork. Through our WordPress troubleshooting service, the team checks whether the email is generated, reads the logs, tests delivery to major inboxes, and reviews the headers to see which check fails. Then we fix the actual cause, whether SMTP, DNS records, a form setting or a conflict after an update, and test everything before closing the ticket.
Prevention is part of the work too. Our maintenance plans include a form functionality check that tests submissions and confirms messages are delivered, alongside core, theme and plugin updates. Plans run Daily at $60, Weekly at $20 or Monthly at $10 per site, and you can enable uptime monitoring as a separate add-on so you hear about downtime as well as silent failures. Our overview of what WordPress maintenance includes explains how the pieces fit together.
Support work is billed through support credits at $42 per hour, with bundles that bring the rate down by up to 21%, and every hour is tracked in the ticket. Agencies can use the same service under their own brand through our white-label WordPress support program, setting their own margin and passing fixed, working email back to their clients.
Frequently Asked Questions
These are the questions we hear most often from site owners and agencies dealing with missing WordPress email. If yours is not covered, the testing steps above are the quickest way to narrow it down.
| Question | Answer |
|---|---|
| Why is WordPress not sending emails when the form says “sent”? | The wp_mail() function returns true when the request is processed, not when the message reaches an inbox, so hosts and receivers can still drop or filter it. |
| Do I need SMTP if my emails sometimes arrive? | Yes. Occasional delivery usually means your mail is borderline on authentication or reputation. An authenticated SMTP provider makes delivery consistent. |
| Do the Gmail and Microsoft 5,000-a-day rules apply to small sites? | The strictest rules target high-volume senders, but Google requires SPF or DKIM from all senders, and Microsoft recommends SPF, DKIM and DMARC for everyone. Google notes that unauthenticated mail is more likely to be marked as spam. |
| Can I send from my Gmail address through my website? | Sending as a free Gmail or Yahoo address from your server fails their DMARC checks. Use an address on your own domain and put personal addresses in Reply-To. |
| Why are WooCommerce order emails missing but other emails work? | Check that the order status actually changes and that the email type is enabled. Then review the transactional-emails log under WooCommerce, Status, Logs to see if the email was sent, failed or never attempted. |
| How often should I test my contact forms? | At least monthly, and after every update, migration, DNS change or new plugin. Email setups usually fail after a change, not on their own. |
Get Your Site Emails Back on Track
Missing emails rarely announce themselves, which is exactly why they cost so much. Moving your site to authenticated SMTP, setting up SPF, DKIM and DMARC, and fixing form From addresses turns a fragile setup into one you can test and trust.
The work does not end with the first fix, either. Plugins update, DNS records change during migrations, and forms get rebuilt. A short monthly test of every form and a quick look at your DMARC reports keep small problems from turning into weeks of lost leads.
If you would rather hand the diagnosis and fix to a team that does this every day, Webueno can find out where your messages are going, fix the cause and test delivery. Create your Webueno account and open a ticket, and we will get your forms, order emails and password resets delivering again.