Quick answer
A form should send through a supported authenticated mail service and use a domain-controlled sender address. Put the visitor's address in Reply-To when the application supports it, rather than impersonating the visitor's domain as From. A success message in the form does not prove delivery.
Before you start
Identify the form plugin or application, mail provider, authorized sender, recipient, and any consent or retention requirements. Use a staging test or clearly labeled controlled submission.
What to do
- Configure the application's supported SMTP or transactional-mail integration using protected server-side credentials.
- Use an authorized From identity and the intended recipient. Set Reply-To to the visitor address only after validating it appropriately.
- Verify the domain's relevant SPF/DKIM configuration and the provider's sender requirements.
- Submit a controlled test and inspect application logs, provider delivery status, and the recipient inbox, including spam or quarantine.
Check the result
Confirm that the message arrived with the expected content and reply behavior. Check failures as well as successful sends, and ensure secrets are absent from public errors and logs.
If something does not work
If a form reports success but no mail arrives, trace the message through each system using time and recipient. Do not repeatedly submit real customer data or disable spam protections to make a test pass.
If ordinary incoming messages are missing too, start with the missing-message delivery checks. If only form notifications fail, keep the controlled submission time, recipient and redacted application or provider error, then contact support with those details.
Contact form not sending email
If a form says success but no email arrives, identify the exact form and notification action first. Confirm that the notification is enabled, its recipient is current, and renamed fields still map to the intended values. A saved submission and a sent email are separate results. For Ninja Forms, inspect Emails & Actions and the active email action; use the form setup guide for its controls.
- Use one clearly labeled sample submission and record its time/time zone. Avoid real customer information and unnecessary attachments.
- Check existing private application/mail-provider logs for the corresponding attempt. A successful WordPress mail-function return generally establishes a handoff, not delivery to the destination inbox.
- If the provider rejected it, keep the exact response and correct the authorized sender, recipient, authentication or applicable limit. If the provider accepted it, trace its message/queue identifier and inspect the recipient's spam/quarantine.
- Verify a fresh controlled submission after the targeted correction. Confirm the actual mailbox, expected fields and Reply-To behavior. Remove temporary diagnostics that expose submitted values or credentials.
If no action ran, investigate the form/application. If normal business mail also fails, use the provider's mailbox and routing checks. Do not change a customer's MX records just to repair a form without first identifying who hosts the business email.
Use the recent delivery report
In cPanel, open Email > Track Delivery, enter the actual recipient and select Run Report. Check the displayed retention window and relevant event-type filters. If no event appears, check the application log or the delivery log of any separate mail provider used by the application.
cPanel screenshot example
View larger screenshot
Track Delivery in cPanel Jupiter. recipient@example.com is sample data. Enter the actual recipient in your own account and select Run Report to search recent delivery events.
Related help
- Understand SPF, DKIM and DMARC for your business domain
- Collect useful evidence when an email message is missing
- Change a WordPress contact-form field and its saved notification mapping
- Send a website support request with useful troubleshooting details
- How to install and set up Ninja Forms in WordPress
- Set local or remote email routing for the correct mail provider
- Find the correct secure IMAP and SMTP settings for your mailbox
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
Symptom guidance and related-help review: November 1, 2026.
Customer symptom and related-help review: November 1, 2026.
