WordPress

WordPress not sending emails? Trace the failure before changing plugins

Diagnose missing WordPress form notifications and password-reset emails by separating form processing, mail handoff, provider delivery and inbox placement.

A visitor sees “Message sent,” but the enquiry never appears in your inbox. Reinstalling the form plugin may not help: the failure could occur after the form has already completed its part.

Treat email as a chain of events. Find the last step you can prove happened before changing the configuration.

1. Identify which messages are missing

Compare a controlled form notification with another WordPress email, such as a password-reset request for your own test account. Use accounts and recipient addresses you control.

If one notification fails while other messages arrive, inspect that form’s recipient, conditions and template settings. If every message fails, investigate the shared sending configuration first.

Use a unique test subject or reference number and record the timestamp. This gives you something specific to locate in application and provider logs.

2. Distinguish submission from delivery

A successful form submission can mean that the entry was accepted. It does not necessarily mean the notification was delivered.

WordPress explicitly documents that a successful wp_mail() return value is not proof that the recipient received the message. See the official wp_mail reference.

Evidence What it establishes
Form entry saved The submission reached the application’s storage path
Mail operation accepted The local sending method processed the request
Provider message ID The provider accepted a message for processing
Delivery event The receiving mail server accepted it, according to the provider
Message visible in inbox The intended mailbox received it in the location you checked

Do not treat those checkpoints as interchangeable. Delivery to a receiving server can still lead to spam placement or filtering.

3. Inspect sender and recipient configuration

Check for typos, retired recipients and conditional routing rules. Verify which address is used as the sender and which address is used for replies.

For contact forms, a common setup is a verified address on your sending domain as the sender, with the visitor’s validated address in Reply-To. Trying to send as an arbitrary visitor’s domain can conflict with that domain’s authentication policy.

Avoid placing unvalidated visitor input directly into email headers. Review the form integration’s documented configuration rather than adding header-building snippets without understanding their handling.

4. Verify the sending provider

If you use an SMTP or API mail integration, confirm that credentials are current and that the configured sender is authorised. Review its error messages for rejected authentication, account limits or unverified domains.

Follow the provider’s instructions for DNS authentication. Use its own verification screen to check the expected records rather than copying values from an unrelated tutorial. Allow for DNS propagation and avoid creating conflicting duplicate records.

Changing transport does not guarantee inbox placement. It gives you a sending route that you can configure and observe.

5. Follow the message through the logs

Look for the test reference and timestamp. Check whether the provider reports a rejection, bounce, suppression or delivery event. Confirm the recipient used by the application matches the one you intended.

If the provider reports delivery, check spam, mailbox rules, forwarding and quarantine with the mailbox owner. If the provider never saw the request, return to the application or transport configuration.

Keep temporary email logging limited to what is necessary. Form bodies and reset links can contain private information; restrict access and remove unnecessary logs after diagnosis.

6. Retest the real workflow

After the fix, test the actual public form, not only the mail plugin’s test button. Check validation, submission storage where supported, notification routing and the final mailbox.

Keep a fallback process for important enquiries. A notification should not be the only evidence that a valuable submission existed if the application supports durable entry storage.

Use the staging release checklist for configuration changes. If the form is also slow, investigate that separately with the WordPress performance guide.