Why am I not getting emails from my WordPress contact form?
Submit one test with a unique subject and follow it to the inbox your team uses. Confirm the form’s notification recipient and sender. Check the outgoing mail service for the same test, then look for an inbox rule, quarantine event, or rejection if the service handed off the message.
What does the problem look like?
A volunteer or customer sees a thank-you message, but the shared inbox stays empty. Some teams discover that the alert reaches an individual mailbox but misses a shared one. Others see regular WordPress messages arrive while a single form stops notifying anyone. Which addresses and forms are affected tells you where to start.
Before you make changes
Back up the site files and database and record the working settings you would restore. Use a protected staging copy and a test inbox you control. Keep normal visitor submissions and outgoing customer alerts disabled on the copy. Confirm that you can edit the form and ask the email administrator to handle message traces or DNS changes.
Step-by-step troubleshooting
Start with one identifiable notification
Open the public contact page while signed out. Submit a dummy inquiry with a unique phrase such as WP-FORM-US-01. Write down the time zone, exact form used, intended recipient, and what the page shows after submission. Leave file uploads out of this first test.
Verify the notification attached to that form
In WordPress, check the matching form and its active notification. Confirm who receives it, whether the notification has send conditions, and whether it uses a verified sender address. If you use Contact Form 7, review the Mail tab. Put the visitor’s validated email field in Reply-To when permitted by the plugin.
Compare a direct mail test with the contact-form result
If the mail integration already provides a test, run it against the same mailbox. Compare both outcomes. A working integration test narrows the investigation toward the individual notification. A failure in both tests calls for checking the configured transport and its own error details.
Trace the message from the outgoing service to the recipient
Look up the test timestamp and address in the mail service’s records. If you use Exchange Online and have the right permissions, trace the message in the Exchange admin center. Examine whether it reached the organization, was rejected or deferred, or was delivered. Follow any reported quarantine or policy rule through the admin console.
Make one targeted adjustment and retest on the public page
Change the setting indicated by the evidence in staging first. After applying the tested fix, submit a new marker from the real form and verify delivery to both the intended inbox and one authorized comparison inbox when useful. Check replies and autoresponders separately.
Worked example
A volunteer organization has a public event inquiry form and a Microsoft 365 shared inbox. A dummy submission reaches a controlled comparison inbox. The Exchange trace for the shared address reports item quarantine. The organization’s administrator reviews the event and resolves the specific rule, keeping other mail protections in place. A fresh WP-FORM-US-02 submission is then found in the shared Inbox, and a team member verifies the reply goes to the dummy sender.
Common mistakes
- Using the visitor’s address as the From address. Use an authorized sender under your sending domain and put the visitor’s address in Reply-To where supported.
- Replacing transport settings, sender, and recipient together. Test one evidence-backed change at a time so you can identify the fix.
- Treating a provider status as proof that a teammate saw the message. Verify the marker in the actual shared inbox and check who has access to it.
- Connecting an unrestricted personal mailbox or leaving full message-body logging enabled. Follow your organization’s settings for credentials, data access, and retention.
Verify the fix and plan a rollback
How to verify the fix
A signed-out test submission reaches the expected team inbox with the same marker and an accurate reply target. Document the send and receipt times. Verify the recipient’s own confirmation independently if your form sends one, and rerun an attachment test if file uploads are part of the published flow.
If the change fails
Remove or revert the specific change if the acceptance check fails. Restore the previous notification, sender, or mail connection from the recorded settings and test a fresh message. Have the email administrator restore prior DNS records if changed. Coordinate a full backup restore with the site owner so that recent submissions, orders, or content changes are preserved where possible.
Practical follow-up questions
Does the contact form’s thank-you message prove email was delivered?
The page confirms what the application was able to process. Use a test marker to confirm the separate mail outcome. WordPress documents that even a successful wp_mail() return can occur without the recipient receiving the message.
How can I tell whether only one form has a bad notification?
Submit dummy entries on both forms to the same authorized mailbox. Compare their settings, delivery event times, and what happens after submission. Check that the public page embeds the intended form rather than an older duplicate.
What do I check if the WordPress password-reset email works?
A successful password reset shows that at least one email flow works. Compare the notification’s recipient, sender, and conditions with a controlled transport test. Review the form’s effective From and Reply-To rules, which may differ from account emails.
Can I route notices from the domain and still reply to the customer?
Yes. Use an approved sender address for From and assign the visitor’s validated field to Reply-To when supported. Deliver a test using an address you control, then open Reply and confirm the destination.
Why does my personal inbox receive the alert while our shared mailbox does not?
Check whether the shared mailbox address is correct and whether it accepts this sender. An authorized administrator can use message trace to find a rejection or redirect. For a delivered result, ask the team to check rules, folders, and shared-mailbox permissions.
What if the email provider says it accepted the message?
Establish which system accepted it and which recipient it handed off to. The sending vendor’s confirmation may occur before the recipient service processes the message. Use the destination provider’s trace or test at the actual mailbox to finish the check.
How should I handle a strict DMARC policy during troubleshooting?
Keep your existing policy in place while reviewing alignment and authentication. Check whether the visible From domain aligns with the domain that passes SPF or DKIM under your DMARC settings. Have the mail administrator review provider-proposed records before publishing changes.
What can I test when the hosting provider does not expose logs?
Use a unique dummy submission and a comparison test from the already configured mail integration if available. Ask the host or email administrator to confirm a delivery attempt, sharing only the time, test recipient, and sanitized error. Check the actual inbox for independent evidence.
Can I retrieve messages people submitted during the outage?
Check the existing form entry database or downstream integration, if it was set up before the incident. A missing email can sometimes be recovered from an entry stored separately. Contact Form 7 by itself does not keep submitted messages.
Why does the form work without an attachment?
Retest with a small permitted dummy file. Compare the form plugin’s upload limits with the recipient’s attachment rules and the transport’s message-size limit. A rejected attachment and an invalid form field require different fixes.
How do we prove the issue is fixed after a web host move?
Test from the active public contact page and check a real receipt in the approved shared inbox. Record the test marker, time, and any transport event ID. Test each critical notification separately, including any staff and visitor templates.
Free tools and website checks
- Website Launch Checklist (German)
Keep a checklist of completed manual checks and export the status as a text file. This checklist does not send email.
- Free Website Checks (German)
Browse the existing checks. If the contact page URL changed, use the linked Redirect Checker to see the HTTP status and redirect chain for that public URL.
Frequently asked questions
Is a new SMTP plugin required to solve this?
Use the existing supported transport if it still works. Change it only when testing shows it is the cause and your host and provider support the replacement.
Should I ask everyone to allowlist my website?
Start with the delivery trace. A mailbox-specific policy may merit a narrowly scoped change by its administrator. Widespread delivery problems usually need investigation of the sending configuration.
Can I test a live intake form with a customer’s details?
Use synthetic details and an address you control. You can verify routing, permissions, and replies without inserting a customer’s information into test logs.
Official references and scope
This guide uses tests and records from services you can access. It cannot inspect your delivery logs or certify inbox placement. If the evidence ends at a rejection or queue event, send your mail administrator the timestamp and redacted error before altering the configuration.
- WordPress Developer Resources · wp_mail()
- WordPress Advanced Administration Handbook · Backups
- Contact Form 7 · Setting up mail
- Contact Form 7 · Best practice to set up mail
- Contact Form 7 · FAQ on submissions and mail delivery
- Gmail Help · Email sender guidelines
- Microsoft Learn · Trace an email message in Exchange Online