Separate submission, application handoff, transport and recipient delivery; repair the failing stage instead of assuming a mailbox subscription guarantees form delivery.
A working form needs a valid submission, a correctly configured notification, a functioning sending route and acceptance by the recipient’s mail system. Check those stages in order. A green success message or a purchased business inbox does not prove that a contact-form notification reached the intended person.
Use a synthetic test message on a site you administer. Avoid real customer information in diagnostics, and keep another contact route visible while the problem is unresolved. This is a researched diagnostic guide; we have not measured a provider’s inbox placement.
A four-stage trace for one test message
| Stage | Evidence to look for | What remains unproven |
|---|---|---|
| 1. Submission | The form validates and the application receives it | Whether a notification was created or sent |
| 2. Application handoff | The correct recipient and notification template are used | Whether the sending service accepted the message |
| 3. Transport | The configured sender’s log or error describes the attempt | Whether the recipient accepted it or placed it in the inbox |
| 4. Recipient | Delivery trace, rejection, quarantine or actual receipt | That every future message will receive the same treatment |
1. Confirm the submission reaches WordPress
Submit one harmless test with a unique label and record the time. Note the exact visible response. A validation error, endless spinner, blocked request and successful submission are different observations. Check recent form, security, caching and script changes when the browser never completes the submission.
Reproduce suspected conflicts on a separate copy rather than disabling the site’s security or every plugin in production. A cache rule affecting a form endpoint can differ from the page-cache settings for a normal article. Follow the form and host documentation for the actual setup.
Check whether your form product stores entries. Contact Form 7 does not store submissions by itself; its optional Flamingo companion creates a separate record. Other products differ. If storage is enabled, define who can read it, what should be collected and when it should be removed. Do not enable unlimited retention just to avoid fixing notifications.
2. Check recipient and sender settings
Open the correct form’s notification settings. Verify the recipient is a real monitored address, the notification is enabled and the submitted fields map to the intended template. Check for a typo, obsolete employee address or an additional notification mistaken for the main one.
Contact Form 7’s mail settings distinguish To, From and additional headers. Its From address should belong to the website domain. The actual sending service must also authorize that sender; merely typing a domain address into a field does not establish permission to send.
For a typical visitor inquiry, use an authorized business-domain sender for the notification and a properly validated visitor address in Reply-To where the product supports it. The developer’s setup guidance explains this separation. Do not impersonate the visitor’s Gmail or other external domain in From.
3. Understand what “sent” actually means
WordPress documents that a true result from wp_mail does not establish successful recipient receipt. It means the sending method processed the request without reporting an error. A form’s success response may therefore precede filtering or rejection elsewhere.
The Contact Form 7 FAQ makes the same practical distinction for its successful response. Record application-level errors separately from transport or recipient outcomes. A sender log saying accepted and a recipient saying “not in my inbox” can both be accurate at different stages.
Identify the active transport: hosting mail, an authenticated SMTP service or a supported sending API. Ask the host what is allowed and inspect the configured service’s error or activity record. Do not paste SMTP passwords, API keys or complete private message bodies into a public support thread.
4. Check authentication with the real sender
Use the actual sending service’s current instructions to review SPF, DKIM and the domain alignment required by DMARC. Website hosting, staff mailboxes, forms and newsletters may use different senders. Changing the mailbox MX record alone is not a general fix for outbound form notifications.
Gmail’s sender guidelines distinguish requirements applying to all senders from additional bulk-sender requirements. Authentication is important, but valid authentication does not guarantee inbox placement. Reputation, message characteristics, recipient policy and sending behavior still matter.
Inventory the legitimate sending services before changing DNS. Do not create multiple independent SPF records or impose a strict rejection policy without understanding existing senders. Use the small-business authentication guide to organize that work with the provider.
5. Trace the recipient outcome
Check spam, quarantine, filtering rules and the correct inbox or shared-address destination. If available, ask the recipient administrator for a trace using the test time and message identifier. A rejection code is more actionable than repeatedly submitting the same form.
Try a small controlled test to another mailbox you own to determine whether the symptom is recipient-specific. Do not create a burst of retries or send tests to unrelated people. A successful alternate delivery narrows the investigation but does not prove universal deliverability.
When sharing headers with support, remove addresses or identifiers that are not needed and follow a private support channel. Preserve the diagnostic distinction between the envelope sender, visible From and Reply-To; replacing them at random can obscure the cause.
What to repair or buy next
If the current sending route cannot meet the documented requirement, consider one supported authenticated transport and verify its sending limits, allowed use, logs, retention and charges. Avoid several competing SMTP plugins. A staff-mailbox plan, a newsletter subscription and transactional sending are different products.
Read email hosting versus email marketing before purchasing a service with the wrong purpose. If the staff inbox itself is missing, compare real mailbox needs and costs separately. If the failure followed a domain connection, review the DNS change.
After repair, repeat the same harmless test from submission to actual receipt and check that customer replies reach the intended address. Record the responsible service and a workable fallback contact route. Treat that result as one verified workflow, not a promise that future mail can never be filtered.
Sources and verification
Editorial review 2026-10-08. Source check dates are recorded separately. Notes describe what each source supports and its limits.
View sources
- WordPress: wp_mail functionChecked A true return value means the sending method processed the request without an error, not that the recipient received it.
Limits: Function documentation, not a delivery test or provider-specific SMTP configuration. - Contact Form 7: FAQChecked A successful form message is not proof of inbox receipt; spam filtering and application failures are separate possibilities.
Limits: Specific to Contact Form 7; response wording and storage differ in other form products. - Contact Form 7: setting up mailChecked Recipient, sender and additional headers are separate fields; the sender should belong to the website domain.
Limits: Specific template syntax; exact sender authorization must also match the actual sending service. - Contact Form 7: mail setup best practiceChecked Use an appropriate domain sender and distinguish the visitor address from the notification sender.
Limits: Recommendations do not prove authentication passes or guarantee inbox placement. - Contact Form 7: saving messages with FlamingoChecked Contact Form 7 alone does not retain submissions; optional local storage provides a separate record.
Limits: Storing submissions creates access, retention and privacy responsibilities; not a recommendation to store everything. - Google: email sender guidelinesChecked Authentication, infrastructure, reputation and sending practices affect mail to personal Gmail accounts; bulk requirements differ.
Limits: Gmail recipient guidance, not a universal deliverability guarantee or a full sending-service specification.