If WordPress is not sending email, start by checking whether every message fails or just one type, such as a contact-form notification, password reset or order email. A form can save a submission even when its notification never reaches you.
Send one test from the mail integration already installed on the site to an inbox you control, then repeat the original notification with harmless test details. If the direct test arrives but the notification does not, check the notification’s recipient and conditions. If both fail, look for the sending error or provider record before changing settings.
This guide follows the message from WordPress to the sending service and the recipient mailbox. A “sent” result alone does not confirm inbox delivery.
Guide reviewed: October 18, 2026. Menu labels use English WordPress; provider-specific controls may differ.
Quick diagnosis
| Test result | Where to look | Next action |
|---|---|---|
| Form entry exists, no mail attempt | Notification rules and recipient | Check enabled notifications and conditions |
| Mail attempt fails, provider has no record | SMTP/API connection and authorized sender | Read the exact sending error |
| Provider shows bounced or rejected | Provider event and recipient response | Fix the stated rejection reason |
| Provider accepted, inbox is empty | Mailbox spam, filters and delivery events | Compare another controlled recipient |
| Direct test works, queued mail does not | Queue and scheduler | Check the background job rather than DNS first |
Check whether the notification was created
- Choose one workflow: form notification, password reset or order email.
- Submit once using test details and record the time.
- Confirm the form entry or triggering event exists.
- Check the notification’s enabled state, recipient and conditions.
- Look for the matching private mail-log event if logging is already available.
For a form, confirm the submission exists and the notification is enabled. For an order, check the order state that should trigger the message. A successful form submission screen is not proof that every notification rule ran.
Review the recipient address and any conditions attached to the notification. A misspelled address or rule that excludes a certain submission can look like a general mail failure. If one notification fails while others arrive, concentrate on that configuration first.
A mail log can help show that WordPress attempted to send the message. Keep such logs private and retain only what you need, since they can contain form data, customer details, and password-recovery links.
Follow the handoff to the sending service
- Open the site’s current mail integration settings.
- Compare the sending service, host or API endpoint and authentication method with that provider’s instructions.
- Send one controlled test and save the exact error or message identifier privately.
- Find that same message in the provider’s activity log by time and recipient.
Use the credentials and encryption method for one provider. Changing SMTP ports at random can hide an authentication or network problem.
WordPress’s wp_mail() function can report success when the sending method processed the request without error. It does not establish final delivery. The mail provider’s activity record gives you a more useful next checkpoint.
If no record appears at the provider, inspect the site’s SMTP or API configuration and the relevant error. Credentials, connection settings, and the authorized sending address need to match that provider’s instructions. Do not combine settings copied from different services.
A dedicated authenticated sending service can offer clearer delivery records than basic web-server mail. It still needs correct configuration and does not guarantee inbox placement. Choose the service based on the site’s actual notification needs and follow its setup documentation.
Use a sender your domain is allowed to use
For a contact form, the visitor’s email belongs in Reply-To when you want to answer them. Using that visitor’s address as the site’s From address can make the message appear to impersonate a domain the site does not control.
Use a consistent authorized sender and configure the domain authentication requested by the sending provider. SPF, DKIM, and DMARC have different roles, and their values need to fit the services that actually send for the domain.
Review existing DNS records before adding or replacing anything. A domain may already use another service for ordinary mailbox email, and a careless change can affect it. Your provider can supply the exact records and verify that the authenticated domain aligns appropriately with the visible sender.
Read the provider’s delivery result
Example diagnostic trail: “Form entry created → mail handed off → provider reports invalid recipient.” That points to the recipient address; reinstalling the form plugin would not repair it. This is an illustrative sequence, not a delivery record from this site.
An accepted message may still be deferred, bounced, suppressed, or delivered to spam. Look up the single test message by time and recipient. A rejection code is more informative than another round of plugin reinstalls.
Check the receiving mailbox’s spam folder and filters, and compare an authorized test recipient at another provider. One provider accepting the message does not prove all recipients will, but it helps identify whether the issue is broad or destination-specific.
Suppression lists can also prevent retries after earlier bounces. Correct the reason for the bounce before requesting removal through the sending service’s supported workflow. Repeatedly sending to an invalid address can worsen reputation and does not repair the destination.
Check background delivery and the actual workflow
Some plugins queue notifications instead of sending them immediately. If a direct test works but queued messages do not, inspect the queue and scheduler. Our WP-Cron guide covers delayed background work.
After the repair, test the original workflow once with a suitable test account or harmless submission. Confirm the message at the provider and in the recipient mailbox. A standalone SMTP test alone does not verify a form’s notification conditions.
Keep the sending method, authorized From address, and successful test in your notes. WordPress’s mail function reference explains its return value, while Google’s sender guidance explains authentication and delivery expectations for Gmail recipients.
What a complete email test includes
Repeat the original form or notification workflow, confirm the provider record, and open the resulting message in the controlled recipient inbox. Test Reply-To if replies are part of the workflow. Record the time and result without retaining unnecessary submission content. WordPress’s wp_mail reference explains why a successful return value does not guarantee delivery.