Your SMTP plugin's test email arrives, but an enquiry submitted through your website never appears. That result narrows the investigation; it doesn't prove the contact form works. The test and the form may use different recipients, sender settings, content or notification rules.
If your SMTP test works but your WordPress contact form doesn't send email, compare the actual form notification with the successful test. Check whether the form creates a notification, which addresses it uses, and what the sending provider records for that specific message.
This guide gives business owners and WordPress administrators a controlled way to investigate. The worksheet and scenarios below are suggested diagnostic exercises, not results from a customer project.
What does a successful SMTP test actually prove?
If you received the test, that particular message reached that particular mailbox at that time. It does not establish that every form uses the same configuration. Even a successful return from wp_mail() only indicates that the sending method processed the request without an error; it does not confirm receipt. See the WordPress wp_mail documentation.
Keep three outcomes separate: the visitor submitted a form, WordPress attempted a notification, and someone received the notification. A success notice is not a substitute for checking all three.
Start with the form that is actually on the page
Open the public contact page in a logged-out browser. Note its URL and identify the embedded form in your editor. A surprisingly easy diagnostic mistake is editing a newer form while the page still embeds an older copy.
- Submit harmless sample information using an email address you control.
- Put a unique reference such as
FORM-CHECK-01in the message. - Record the time and timezone, the visible response and the expected recipient.
- If entry storage is enabled, find the matching record.
- Check the form's notification settings and any available sending logs.
If the page displays a validation error or never finishes submitting, investigate that response first. An SMTP change cannot repair a required field that rejects the submission. Ask your developer to inspect the failed browser request when the page itself supplies no useful explanation.
Do not assume missing email means a saved enquiry exists. Contact Form 7 does not store submitted messages by itself; its developer identifies Flamingo as a separate option for storage in the Contact Form 7 FAQ. Check your own form system before promising to recover past leads.
Compare the working test and failed notification
| Item | Successful SMTP test | Actual form notification |
|---|---|---|
| Recipient | Mailbox where the test arrived | Address after form rules resolve |
| From address | Sender shown on the received email | Sender the notification actually uses |
| Reply-To | Record it if present | Visitor field or fixed address |
| Message contents | Simple test body | Template, links and attachments |
| Trigger | Manual test button | Form rule or queued action |
| Evidence | Received email and timestamp | Entry, send attempt and provider event |
Change one difference at a time and repeat the public form submission. If you change the recipient, template and mailer together, a successful result won't tell you which change helped.
Check the recipient and notification rules
Confirm that the administrator notification is enabled. Inspect the actual recipient field rather than assuming it inherits the WordPress administration email address. Check for a former employee's address, a misspelling, or a dynamic field that becomes blank.
For forms with routing rules, make a small list of branches: Sales, Support and Careers, for example. Test each separately. If Sales works but Careers fails, that is a more useful clue than saying the entire website cannot send email.
Where your plugin supports conditional notifications, temporarily simplify the rule on a staging copy. Use one fixed recipient you control. Preserve the original settings so you can restore the intended routing after diagnosis.
A Contact Form 7 example: From and Reply-To
In Contact Form 7, open the relevant form's Mail tab. The plugin's mail configuration documentation describes the recipient, sender and additional-header fields. Its mail setup guidance explains why sender identity matters.
For a fictional business using example.com, a starting arrangement is:
- To:
enquiries@example.com, a real monitored mailbox. - From:
Website Enquiries <forms@example.com>, authorized by the sending provider. - Additional headers:
Reply-To: [your-email].
Replace the example addresses. Use [your-email] only if your form contains that correctly named email field. Resolve configuration warnings and validate the submitted email address. The visitor's address belongs in Reply-To, not in a From field that pretends your website can send on behalf of the visitor's domain.
Check the received message too: a mailer setting can override the configured sender. If Mail (2) is enabled, test that acknowledgement separately. Contact Form 7 sends Mail (2) only after the primary Mail succeeds; that still does not establish inbox receipt.
Use the provider's evidence to choose the next action
Look for the specific test message in the sending service, matching time, recipient and message identifier where available. A WordPress log and a provider log describe different parts of the journey.
- No matching attempt: return to notification generation, routing or the integration path. First confirm you are checking the correct account and time range.
- Rejected attempt: use the exact error to investigate sender authorization, account access or a message restriction.
- Queued or deferred: check the provider's explanation and retry behaviour.
- Destination accepted: check spam, quarantine, forwarding and mailbox rules with the recipient administrator.
If the basic template works but the normal one fails, restore links and attachments individually. Keep a record of the first failing version. Don't send customer documents as test attachments.
When should you investigate SPF, DKIM and DMARC?
Investigate authentication when the provider reports authentication problems, when sender details differ between tests, or when messages reach spam instead of the inbox. SPF authorizes sending infrastructure, DKIM provides a domain signature, and DMARC checks alignment with the visible From domain and specifies handling policy.
Google's email sender guidelines distinguish requirements for all senders from additional bulk-sender requirements. They recommend SPF, DKIM and DMARC. Follow your provider's exact DNS instructions and inspect authentication results on a received message; a record existing in DNS is not proof that this particular message passed.
A successful SMTP login does not prove domain authentication or inbox placement. Ask whoever manages DNS to review changes against your other legitimate sending services before editing records.
Worked example: a Chennai service business
Imagine a repair business whose SMTP test reaches the owner's mailbox, but enquiries from a quote form disappear. This is a hypothetical investigation.
The owner checks the embedded form and discovers two notification routes: general enquiries go to the current team, while installation requests go to an old address. They send one controlled submission through each route, confirm the difference, update the installation recipient and repeat both tests.
Next, they reply to the notification to confirm it reaches the test visitor. Finally, they assign one person to review saved enquiries each morning. The useful improvement is a verified route and an owner for follow-up, not another plugin installed without a diagnosis.
Our business website planning guide addresses the broader website. Add form acceptance testing to that plan: attracting a visitor only helps when their enquiry reaches someone who can act.
A practical acceptance test before closing the issue
Use this proposed checklist after the repair. It is a project acceptance standard, not a guarantee of future delivery.
- Submit from the public page on desktop and mobile.
- Test every notification branch with sample data.
- Confirm stored entries where storage is configured.
- Verify the intended recipient receives each notification.
- Reply and confirm the response reaches the test visitor.
- Test any acknowledgement and allowed attachment separately.
- Record the changed setting, result and person responsible for future checks.
Repeat a controlled test after changes to the form, hosting, DNS or sending account. Restrict access to enquiry logs and keep only what your team needs. Avoid retaining complete message contents indefinitely just because logging is available.
If staff need shared ownership and status tracking after enquiries arrive, our small-business help desk comparison covers that next decision. It does not replace fixing delivery first.
What to send your developer
Provide the public form URL, form and mailer plugin names, the test reference, timestamp with timezone, visible response, intended recipient and redacted error. State whether the SMTP test arrived and whether a form entry was saved. Keep passwords and API keys out of screenshots.
If the evidence points to conflicting hooks or custom notification logic, explore our WordPress plugin development and integration services. For help tracing an existing failure, send Innovative Code Tech your form troubleshooting details. Start with the evidence above so the investigation can focus on the failing step.
Frequently asked questions
Why does my SMTP test work but my contact form email fail?
The form may use different addresses, notification rules or message contents. Compare the successful test with one identifiable public form submission, then check the related send attempt.
Does a green success message prove the email arrived?
No. Read the plugin's meaning for that response and verify delivery independently. WordPress processing a mail request successfully does not prove that a person received it.
Can I recover enquiries from before the fix?
Only if a system retained them, such as form-entry storage, a CRM or accessible email records. Installing storage now cannot reconstruct messages that were never retained.
Should I replace my contact form plugin?
Not as the first diagnostic step. Identify the failing stage and test a specific correction. Replacement may be justified if the existing tool cannot meet your workflow or reliability needs.
Is this different from a WooCommerce payment problem?
Yes. Email delivery and payment status are separate checks. A missing notification does not establish whether money was captured. For that situation, use our Razorpay payment and WooCommerce pending-order guide.
Your next action: run one marked submission through the real form and complete the comparison worksheet. Follow the evidence until you can show where the message stopped, then retest the complete enquiry workflow.
